Systems, apparatus, and methods for detecting an environmental anomaly and initiating an enhanced automatic response using elements of a wireless node network and using sensor data from id nodes associated with packages and environmental threshold conditions per package

ABSTRACT

An improved system detects an environmental anomaly in a shipping container and initiates a mediation response through a generated layered alert notification. The system includes sensor-based ID nodes associated with packages within the container, and a command node mounted to the container communicating with the ID nodes and an external transceiver on a vehicle transporting the container. The command node is programmed to detect sensor data from the ID nodes; compare the sensor data to package environmental thresholds in context data related to each ID node; detect the environmental anomaly when the comparison indicates an environmental condition for at least one package exceeds its environmental threshold; responsively generate a layered alert notification identifying a mediation recipient and mediation action, and establishing a mediation response priority based upon the comparison; and transmit the layered alert notification to the transceiver unit to initiate a mediation response related to the mediation action.

PRIORITY AND RELATED APPLICATIONS

The present application hereby claims the benefit of priority to relatedU.S. Provisional Patent Application No. 62/735,075 and entitled“Improved Systems, Apparatus, and Methods for Detecting an EnvironmentalAnomaly and Initiating an Enhanced Automatic Response Using Elements ofa Wireless Node Network.”

The present non-provisional application is also related in subjectmatter to the following U.S. non-provisional patent applications whereeach also claims the benefit of priority to the same above-referencedprovisional patent application: (1) Non-Provisional patent applicationSer. No. ______, entitled “Improved Systems, Apparatus, and Methods forDetecting an Environmental Anomaly and Initiating an Enhanced AutomaticResponse Using Elements of a Wireless Node Network Using ID Nodes andEnvironmental Threshold Conditions Per ID Node”; (2) Non-Provisionalpatent application Ser. No. ______, entitled “Improved Systems,Apparatus, and Methods for Detecting an Environmental Anomaly andInitiating an Enhanced Automatic Response Using Elements of a WirelessNode Network Including a Command Node Having a Command NodeEnvironmental Sensor”; (3) Non-Provisional patent application Ser. No.______, entitled “Methods and Systems for Unresponsive ID NodeMonitoring for an Environmental Anomaly”; (4) Non-Provisional patentapplication Ser. No. ______, entitled “Systems and Methods for Internaland External Monitoring for an Environmental Anomaly Within a ShippingContainer and Reporting to an External Transceiver to Initiate aMediation Response;” (5) Non-Provisional patent application Ser. No.______, entitled “Systems and Methods for Internal and ExternalMonitoring for an Environmental Anomaly Within a Shipping Container withResponsive Reporting to an External Transceiver and Initiating aMediation Response Directly with an Onboard Fire Suppression System”;(6) Non-Provisional patent application Ser. No. ______, entitled“Methods, Systems, and Enhanced Shipping Container Apparatus Assemblyfor Monitoring for an Environmental Anomaly Using a Selectively AssignedGroup of ID Nodes in a Wireless Node Network”; (7) Non-Provisionalpatent application Ser. No. ______, entitled “Systems and Methods forAdaptively Monitoring for an Environmental Anomaly Using a DesignatedBridging ID Node for a Remote Monitor Beacon”; (8) Non-Provisionalpatent application Ser. No. ______, entitled “Enhanced ShippingContainer Apparatus for Sensor-based Self-Monitoring, Detecting, andReporting on an Environmental Anomaly”; (9) Non-Provisional patentapplication Ser. No. ______, entitled “Systems and Methods for AdaptiveMonitoring for an Environmental Anomaly in a Shipping Container UsingElements of a Wireless Node Network;” (10) Non-Provisional patentapplication Ser. No. ______, entitled “Dynamically Transitioning Systemfor Monitoring a Shipping Container for an Environmental Anomaly Relatedto the Shipping Container”; (11) Non-Provisional patent application Ser.No. ______, entitled “Improved Systems for Coordinated Mediation Actionin Response to an Identified Environmental Anomaly on a ShippingContainer”; (12) Non-Provisional patent application Ser. No. ______,entitled “Enhanced Shipping Container Apparatus having Integrated FireSuppression and Systems Using the Same for Detecting and Responding toan Environmental Anomaly within the Container”; (13) Non-Provisionalpatent application Ser. No. ______, entitled “Node-enabled BatteryApparatus and Packaging Systems with Integrated Environmental Detectionand Reporting, and Improved Systems for Coordinated Mediation Action inResponse to an Environmental Anomaly Using the Same”; (14)Non-Provisional patent application Ser. No. ______, entitled “Systemsfor Layered Initiation of a Mediation Response to a Battery RelatedEnvironmental Anomaly within a Shipping Container;” (15) Non-Provisionalpatent application Ser. No. ______, entitled “Systems, Apparatus, andMethods for Detecting and Verifying an Environmental Anomaly UsingMultiple Command Nodes”; (16) Non-Provisional patent application Ser.No. ______, entitled “Systems and Methods for Securely Monitoring aShipping Container for an Environmental Anomaly”; (17) Non-Provisionalpatent application Ser. No. ______, entitled “Systems and Apparatus forEnhanced Detection of an Environmental Anomaly Related to a ShippingContainer Using a Node-Enhanced Detection Blanket”; (19) Non-Provisionalpatent application Ser. No. ______, entitled “Systems and Methods forAdaptive Monitoring of a Shipping Container for an EnvironmentalAnomaly”; and (19) Non-Provisional patent application Ser. No. ______,entitled “Apparatus and Systems for Detecting an Environmental AnomalyRelated to a Shipping Container Using a Package Command Node.”

FIELD OF THE DISCLOSURE

The present disclosure generally relates to systems, apparatus andmethods in the field of detecting an environmental anomaly onboard acontainer and responsively initiating an improved mediation response. Inparticular, the present disclosure relates to various aspects involvingsystems, apparatus and methods for improved environmental anomalydetection, related enhanced layered alerting as part of a mediatedresponse, and initiating layered types of mediation responses to such anenvironmental anomaly using one or more elements of an adaptive,context-aware wireless node network.

BACKGROUND

Transporting items, objects, or materials (collectively and generallyreferred to herein as “packages” whether the items, objects, ormaterials are wrapped in packaging material or the items, objects, ormaterials are being shipped without packaging material) is an importantpart of commerce. In some instances, the type of item being transportedmay involve an item, object, or material that may be caustic, flammable,incendiary (e.g., easy to catch fire), or have a composition thatinherently may pose some danger when transporting the item, object ormaterial. For example, the transportation and shipment for certain typesof batteries (e.g., lithium-based or lithium-ion batteries) may incurthe risk of creating an environmental anomaly (such as a fire,explosion, chemical leak, or radiation leak).

Common techniques for monitoring the condition of what is being shippedwithin a shipping container may involve sensors remote from the shippingcontainer. Such monitoring techniques may be located too far away, whichmay cause a lag or undesirable delay in detecting any type ofenvironmental anomaly associated with what is being shipped or justmaintained within the shipping container (e.g., a unit load device (ULD)type of container, an intermodal shipping container, a palletizedcontainment for shipping one or more packages, a storage facility thatmay temporarily maintain packages as a non-mobile type of shippingcontainer, and the like). Such an environmental anomaly may involveextremely hot and caustic conditions that may rapidly spread. As aresult, any delay in detecting such an environmental anomaly isinherently risky and adverse environmental conditions may rapidlyintensify and spread so as to cause damage to the package, container,other packages in the container, other nearby containers, the transitvehicle transporting the container, and possible injury and loss of lifeto those operating the transit vehicle or manipulating the shippingcontainer. Furthermore, any delay in assessing the risk from such anenvironmental anomaly as well as putting a mediation plan into action toaddress the environmental anomaly also increases the undesired severityof any environmental anomaly and its ability to rapidly intensify,spread so as to cause rapid damage to the package, container, otherpackages in the container, other nearby containers, the transit vehicletransporting the container, and possible injury and loss of life tothose operating the transit vehicle or manipulating the shippingcontainer

Accordingly, those skilled in the art will appreciate that whentransporting certain types of items, objects, and materials, the abilityto quickly detect any environmental anomaly is important as time is ofthe essence. This is even more true when transporting packages (e.g.,items, objects, materials) on aircraft where the existence of anyenvironmental anomaly may be catastrophic in the damage it causes andloss of property and life due to any delay in detecting such anenvironmental anomaly, as well as any resulting delay in causing orinitiating a response or mediation action to address the detectedanomaly.

To address these requirements, a variety of systems, apparatus, andmethods are needed that may improve and enhance environmental anomalydetection—especially, onboard a shipping container with one or morepackages—and improve how to respond to such a detected environmentalanomaly. Thus, there remains a need for improved systems, apparatus, andmethods that may provide more extensive and robust detection of anenvironmental anomaly and automated generation of layered alerts andadaptive initiation of one or more mediation responses in a more timelyand integrated manner than previously thought possible.

SUMMARY

In the following description, certain aspects and embodiments willbecome evident. It should be understood that the aspects andembodiments, in their broadest sense, could be practiced without havingone or more features of these aspects and embodiments. It should beunderstood that these aspects and embodiments are merely exemplary.

One aspect of the disclosure presents an improved monitoring system fordetecting an environmental anomaly in a shipping container thatmaintains packages and for reporting a layered alert notificationrelated to the environmental anomaly to an external transceiver unitassociated with a transit vehicle transporting the shipping container.In general, this system comprises a plurality of ID nodes disposedwithin the shipping container and a command node mounted to the shippingcontainer. Each of the ID nodes is associated with a respective one ofthe packages maintained within the shipping container, and each of theID nodes comprises at least an ID node processing unit (e.g., aprocessor), an ID node memory coupled to the processing unit, anenvironmental sensor, and a wireless radio transceiver operativelycoupled to the ID node processing unit. The ID node memory maintains atleast an ID node monitoring program code that programmatically adaptsthe ID node beyond that of a generic computer. The ID node'senvironmental sensor is configured to generate sensor data related to anenvironmental condition of the respective package associated with thatID node. The wireless radio transceiver (whether implemented inhardware, a combination of hardware and software, or as a softwaredefined radio (SDR)) is configured to access the sensor data generatedby the environmental sensor and broadcast the sensor data in response toa report command from the ID node processing unit when the ID nodeprocessing unit executes the ID node monitoring program code.

The system's command node comprises at least a command node processingunit, a command node memory coupled to the command node processing unit,and two communication interfaces (each of which may be implemented inhardware, a combination of hardware and software, or as an SDR). Thecommand node's memory maintains a command node container managementprogram code and context data related to each of the ID nodes, where thecontext data includes at least a plurality of environmental thresholdconditions respectively corresponding to each of the packages. The firstcommunication interface is operatively coupled to the command nodeprocessing unit is configured to communicate with each of the ID nodesusing a first wireless communication format compatible with the wirelessradio transceiver on each of the ID nodes. The second communicationinterface is operatively coupled to the command node processing unit isconfigured to communicate with the external transceiver unit associatedwith a transit vehicle using a second wireless communications format.

As such, the command node processing unit is programmaticallyconfigured, when executing the command node container management programcode, to be operative to detect the sensor data broadcasted from the IDnodes using the first communication interface; compare the detectedsensor data from each of the ID nodes and the respective context datarelated to each of the ID nodes; detect the environmental anomaly forthe shipping container when the comparison of the detected sensor dataand the context data indicates an environmental condition for at leastone of the packages exceeds its respective environmental thresholdcondition; generate a layered alert notification related to theenvironmental anomaly for the shipping container in response todetecting the environmental anomaly (where the layered alertnotification identifies a targeted mediation recipient, identifies atargeted mediation action, and establishes a mediation response prioritybased upon the comparison of the received sensor data and the contextdata); and cause the second communication interface to transmit thelayered alert notification to the external transceiver unit to initiatea mediation response related to the targeted mediation action. As such,the layered alert notification is not merely reporting the detectedanomaly but is proactively and interactively instructing the externaltransceiver to take a specific mediation response related to what thecommand node identifies as the targeted mediation action.

In another aspect of the disclosure, an improved method is described formonitoring a shipping container and responding to an environmentalanomaly using a wireless node network having at least a plurality of IDnodes disposed within the shipping container and a command node mountedto and associated with the shipping container. Each of the ID nodes hasat least one environmental sensor and is associated with a respectiveone of a plurality of packages maintained within the shipping container,and where the command node being operative to communicate with each ofthe ID nodes and an external transceiver unit associated with a transitvehicle. The method begins with generating, by the environmental sensoron each of the ID nodes, sensor data related to an environmentalcondition of the respective package associated with each of the ID nodesas the packages reside within the shipping container. Next, the methodhas each of the ID nodes broadcasting the generated sensor data. Themethod proceeds with the command node detecting the sensor databroadcasted from the ID nodes and comparing the detected sensor datafrom each of the ID nodes and locally maintained context data related toeach of the ID nodes. Such context data includes at least a plurality ofenvironmental threshold conditions respectively corresponding to thepackages. The method then proceeds with the command node detecting theenvironmental anomaly for the shipping container when the comparison ofthe detected sensor data and the respective context data indicates anenvironmental condition for at least one of the packages exceeds itsrespective environmental threshold condition. The command node thengenerates a layered alert notification related to the environmentalanomaly for the shipping container in response to detecting theenvironmental anomaly, where the layered alert notification identifies atargeted mediation recipient, identifies a targeted mediation action,and establishes a mediation response priority based upon the comparisonof the received sensor data and the context data. The method then hasthe command node transmitting the layered alert notification to thetransceiver unit to initiate a mediation response related to thetargeted mediation action (as opposed to merely reporting on thedetected environmental anomaly).

In still another aspect of the disclosure, a more detailed system isdescribed for detecting, automatically reporting on and proactivelyresponding to an environmental anomaly in a shipping container onboard atransit vehicle, where the shipping container maintains packages beingtransported on the vehicle. In general, this system has multiple IDsensor nodes disposed within the shipping container, a command nodemounted to the shipping container, and a transit vehicle transceivermounted on the transit vehicle. Each of the ID sensor nodes isassociated with a respective one of the packages maintained within theshipping container, and each of the ID sensor nodes has an ID sensornode processing unit (e.g., a processor, such as a microprocessor,microcontroller, or other such programmable logic circuitry), an IDsensor node memory coupled to the ID sensor node processing unitmaintaining at least an ID sensor node monitoring program code, at leastone environmental sensor, and a wireless radio transceiver. The IDsensor node's environmental sensor is configured to generate sensor datarelated to an environmental condition of the respective packageassociated with the particular the ID sensor node. The ID sensor node'swireless radio transceiver (whether implemented in hardware, acombination of hardware and software, or as a software defined radio(SDR)) is coupled to the ID sensor node processing unit, and configuredto access the sensor data generated by the node's environmentalsensor(s) and broadcast the sensor data in response to a report commandfrom the ID sensor node processing unit when the ID sensor nodeprocessing unit executes the ID sensor node monitoring program code.

The system's command node has at least a command node processing unit,memory coupled to its processor, and at least two wireless communicationinterfaces (each of which may be implemented in hardware, a combinationof hardware and software, or as a SDR). The command node's memorymaintains at least command node container management program code (thatprogrammatically adapts and specially configures the command node forunique and unconventional operation when executed) and context datarelated to each of the ID sensor nodes. The context data includesenvironmental threshold conditions respectively corresponding to each ofthe packages. A first communication interface is coupled to the commandnode processing unit, and configured to communicate with each of the IDsensor nodes using a first wireless communication format compatible withthe wireless radio transceiver on each of the ID sensor nodes. A secondcommunication interface is also coupled to the command node processingunit, and configured to communicate over a second wirelesscommunications format

The transit vehicle transceiver on the vehicle is in communication withthe second communication interface of the command node, and has at leasta display interface and a fire suppression system interface.

The command node processing unit is programmatically configured, whenexecuting the command node container management program code, to beoperative to detect the sensor data broadcasted from the ID sensor nodesusing the first communication interface; compare the detected sensordata from each of the ID sensor nodes and the context data related toeach of the ID sensor nodes; detect the environmental anomaly for theshipping container when the comparison of the detected sensor data andthe context data indicates an environmental condition for at least oneof the packages exceeds its respective environmental thresholdcondition; generate a layered alert notification related to theenvironmental anomaly for the shipping container in response todetecting the environmental anomaly (where the layered alertnotification identifies a targeted mediation recipient, identifies atargeted mediation action, and establishes a mediation response prioritybased upon the comparison of the received sensor data and the contextdata); and cause the second communication interface to transmit thelayered alert notification to the transit vehicle transceiver toinitiate a mediation response related to the targeted mediation action.

In response to receiving the layered alert notification from the commandnode, the transit vehicle transceiver is operative to automaticallygenerate a mediation message as the mediation response, where such amediation message reflects the targeted mediation action (e.g.,triggering a fire suppression system to initiate via its firstsuppression system interface) and the mediation response priority, andprovide the mediation message to the targeted mediation recipient.

Each of these aspects respectively effect improvements to the technologyof monitoring for and detecting environmental anomalies and how to morerobustly and quickly respond to any such detected environmentalanomalies. Additional advantages of this and other aspects of thedisclosed embodiments and examples will be set forth in part in thedescription which follows, and in part will be obvious from thedescription, or may be learned by practice of the invention. It is to beunderstood that both the foregoing general description and the followingdetailed description are exemplary and explanatory only and are notrestrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments according toone or more principles of the invention and together with thedescription, serve to explain one or more principles of the invention.In the drawings,

FIG. 1 is a diagram of an exemplary wireless node network in accordancewith an embodiment of the invention;

FIG. 2 is a more detailed diagram of an exemplary wireless node networkin accordance with an embodiment of the invention;

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention;

FIG. 4 is a more detailed diagram of an exemplary master node device inaccordance with an embodiment of the invention;

FIG. 5 is a more detailed diagram of an exemplary server in accordancewith an embodiment of the invention;

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 8 is a state diagram illustrating exemplary states and transitionsbetween the states as part of operations by an exemplary node in awireless node network in accordance with an embodiment of the invention;

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment of the invention;

FIG. 10 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-ID node association in accordancewith an embodiment of the invention;

FIG. 11 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-master node query in accordancewith an embodiment of the invention;

FIG. 12 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary alert advertising mode in accordancewith an embodiment of the invention;

FIG. 13 is a diagram illustrating an exemplary location determinationusing master node advertise in accordance with an embodiment of theinvention;

FIG. 14 is a diagram illustrating an exemplary location determinationusing ID node advertise in accordance with an embodiment of theinvention;

FIG. 15 is a diagram illustrating an exemplary location determinationthrough triangulation in accordance with an embodiment of the invention;

FIG. 16 is a diagram illustrating an exemplary location determinationthrough chaining triangulation in accordance with an embodiment of theinvention;

FIG. 17 is a flow diagram illustrating an exemplary method for locatinga node in a wireless node network based upon observed signal patternsand characteristic indications over a period of time in accordance withan embodiment of the invention;

FIG. 18 is a flow diagram illustrating an exemplary method for locationdetermination by varying a power characteristic of nodes in a wirelessnode network in accordance with an embodiment of the invention;

FIG. 19 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 20 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 21 is a flow diagram illustrating yet another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 22 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention;

FIG. 23 is a flow diagram illustrating an exemplary method fordetermining a location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention;

FIG. 24A is a diagram of an exemplary wireless node network used fordetecting environmental anomalies using a command node and ID nodesdisposed within a shipping container in accordance with an embodiment ofthe invention;

FIG. 24B is a diagram of another exemplary wireless node network usedfor detecting environmental anomalies using a command node and ID nodesassociated with packages disposed within a shipping container inaccordance with an embodiment of the invention;

FIG. 24C is a diagram of another exemplary wireless node network usedfor detecting environmental anomalies using a command node and ID nodesgeographically dispersed within a shipping container in accordance withan embodiment of the invention;

FIG. 25A is a diagram illustrating multiple shipping containers in theform of exemplary ULD containers, as loaded into a cargo storage of anaircraft in accordance with an embodiment of the invention;

FIG. 25B is a diagram illustrating multiple exemplary shippingcontainers in a cargo storage of an aircraft having an exemplary firesuppression system onboard that selectively and responsively deploys aspart of a mediation response to a detected environmental anomaly inaccordance with an embodiment of the invention;

FIG. 25C is a diagram illustrating further exemplary externaltransceivers disposed in various control compartments of an exemplaryaircraft transit vehicle in accordance with an embodiment of theinvention;

FIG. 26 is a more detailed diagram of an exemplary command node devicein accordance with an embodiment of the invention;

FIG. 27 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network using sensor data from ID nodes associated withpackages and with environmental threshold conditions for the packages inaccordance with an embodiment of the invention;

FIG. 28 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network using sensor data from ID nodes that are disposedwithin the shipping container but not associated with particularpackages and with environmental threshold conditions for the ID nodes inaccordance with an embodiment of the invention;

FIG. 29 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network using ID node sensor data from ID nodes that aredisposed within the shipping container but are generally not associatedwith particular packages and with environmental threshold conditions forthe ID nodes as well as command node sensor data from a command nodemounted to the shipping container in accordance with an embodiment ofthe invention;

FIG. 30 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network based upon unanticipated communications from IDnodes that are disposed within the shipping container in accordance withan embodiment of the invention;

FIG. 31 is a diagram of another exemplary wireless node network used fordetecting environmental anomalies using a command node associated with ashipping container being transported on a transit vehicle and ID nodesinternal and external to the shipping container on the transit vehicleand where the ID nodes are each associated with packages in accordancewith an embodiment of the invention;

FIG. 32A-32C are a series of diagrams of an exemplary onboard firesuppression system that may be activated and deployed on a transitvehicle for initiating a mediation action in response to a detectedenvironmental anomaly related to a shipping container being transportedon the transit vehicle in accordance with an embodiment of theinvention;

FIG. 33 is a diagram of yet another exemplary wireless node network usedfor detecting environmental anomalies using a command node associatedwith a shipping container being transported on a transit vehicle and IDnodes internal and external to the shipping container on the transitvehicle and where the ID nodes are not specifically associated withpackages in accordance with an embodiment of the invention;

FIG. 34 is a diagram of yet another exemplary wireless node network usedfor detecting environmental anomalies using a command node associatedwith a shipping container being transported on a transit vehicle and IDnodes internal and external to the shipping container on the transitvehicle and where the ID nodes in the network are a combination ofpackage and non-package ID nodes within and outside of the shippingcontainer in accordance with an embodiment of the invention;

FIG. 35 is a flow diagram illustrating an exemplary method formonitoring for an environmental anomaly related to a shipping containerusing a wireless node network having at least a command node associatedwith a shipping container and ID nodes within the shipping container andoutside the shipping container and where the ID nodes are notspecifically associated with packages in accordance with an embodimentof the invention;

FIG. 36 is a flow diagram illustrating an exemplary method formonitoring for an environmental anomaly related to a shipping containerusing a wireless node network having at least a command node associatedwith the shipping container, ID nodes within the shipping container andoutside the shipping container, and an onboard fire suppression systemand external transceiver in accordance with an embodiment of theinvention;

FIGS. 37A-37B are diagrams of an exemplary shipping container thatleverages an exemplary wireless node network for detecting environmentalanomalies associated with the shipping container using a command nodemounted to the shipping container and selectively assigned ID nodeswithin the shipping container in accordance with an embodiment of theinvention;

FIGS. 38A-38B are diagrams of an exemplary shipping container thatleverages an exemplary wireless node network for detecting environmentalanomalies associated with the shipping container using a command nodemounted to the shipping container and selectively reassigned ID nodeswithin the shipping container when what is in shipping container changesin accordance with an embodiment of the invention;

FIG. 39 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using acommand node mounted to the shipping container and selective ones of aplurality of ID nodes disposed at different locations within theshipping container in accordance with an embodiment of the invention;

FIG. 40 is a diagram of an exemplary external transceiver that may beactivated and deployed on a transit vehicle for initiating a mediationaction in response to a detected environmental anomalies related to ashipping container being transported on the transit vehicle inaccordance with an embodiment of the invention;

FIGS. 41A-41D are diagrams of an exemplary enhanced shipping containerthat transports packages and self-monitors for an environmental anomalyusing selectively assigned ID nodes in accordance with an embodiment ofthe invention;

FIGS. 42A-42C are diagrams of an exemplary shipping container thatleverages an exemplary wireless node network for detecting environmentalanomalies associated with the shipping container using a command nodemounted to the shipping container and selectively assigned ID nodeswithin the shipping container as a group of monitor beacons including adedicated bridging node for a remote monitor beacon in accordance withan embodiment of the invention;

FIG. 43 is a flow diagram illustrating an exemplary method foradaptively monitoring for an environmental anomaly using a group ofmonitor beacons including a dedicated bridging node for a remote monitorbeacon in accordance with an embodiment of the invention;

FIG. 44 is a diagram of an exemplary enhanced shipping container thattransports packages and self-monitors for an environmental anomaly usingsensor-based ID nodes in accordance with an embodiment of the invention;

FIGS. 45A-45B are diagrams of an exemplary adaptive wireless nodenetwork system for monitoring a shipping container for an environmentalanomaly using a primary command node and a designated survivor commandnode in accordance with an embodiment of the invention;

FIGS. 46A-46B are diagrams of an exemplary adaptive wireless nodenetwork system for monitoring a shipping container for an environmentalanomaly using a primary command node and multiple prioritized survivorcommand nodes in accordance with an embodiment of the invention;

FIG. 47 is a flow diagram illustrating an exemplary method foradaptively monitoring a shipping container for an environmental anomalyusing a primary command node and a designated survivor command node inaccordance with an embodiment of the invention;

FIGS. 48A-48C are diagrams of an exemplary dynamic monitoring system foridentifying and responding to an environmental anomaly related to ashipping container using wireless ID nodes, a command node as a primarymonitor and external master node that is operative to temporarilyoperate as the primary monitor for the environmental anomaly inaccordance with an embodiment of the invention;

FIGS. 49A-49B are diagrams illustrating primary monitor transitionswithin an exemplary dynamic monitoring system for identifying andresponding to an environmental anomaly related to a shipping containerusing wireless ID nodes, a command node as a primary monitor andexternal master node that is operative to temporarily operate as theprimary monitor for the environmental anomaly in accordance with anembodiment of the invention;

FIGS. 50A-50C are a series of diagrams of another exemplary onboard firesuppression system having an integrated master node and be activated anddeployed on a transit vehicle for monitoring for an environmentalanomaly and initiating a mediation action in response to a detectedenvironmental anomaly related to a shipping container being transportedon the transit vehicle in accordance with an embodiment of theinvention;

FIG. 51 is a diagram illustrating an exemplary onboard fire suppressionsystem having an integrated master node coupled to exemplary shippingcontainer sensors that may be deployed as part of the fire suppressionsystem to provide for further monitoring and assessment of anenvironmental anomaly related to a shipping container in accordance withan embodiment of the invention;

FIG. 52 is a diagram illustrating still another exemplary onboard firesuppression system having a pressurized fire suppression materialcontainer and a controlled release nozzle that can be actuated todeliver fire suppression material to a shipping container beingmonitored by the master node-enabled fire suppression system inaccordance with an embodiment of the invention;

FIGS. 53A-53D are a series of diagrams of exemplary shipping containersthat may be deployed in accordance with an embodiment of the invention;

FIG. 54 is a diagram illustrating an exemplary shipping containerenhanced with an exemplary fire suppression panel implemented within oras part of one of the container's walls in accordance with an embodimentof the invention;

FIG. 55 is a diagram illustrating an exemplary shipping containerenhanced with an alternative exemplary fire suppression panel attachedto one of the container's walls in accordance with an embodiment of theinvention;

FIGS. 56A-56D are a series of diagrams illustrating details of andoperations involving an enhanced shipping container having at least onefire suppression panel and as used in an improved system for coordinatedmediation action in response to an identified environmental anomalyrelated to the shipping container in accordance with an embodiment ofthe invention;

FIG. 57 is a diagram illustrating an exemplary node-enabled batterysystem having integrated environmental detection and reportingfunctionalities in accordance with an embodiment of the invention;

FIG. 58 is a diagram illustrating an exemplary node-enabled packagesystem for a battery having integrated environmental detection andreporting functionalities in accordance with an embodiment of theinvention;

FIG. 59 is a diagram illustrating an exemplary improved system forcoordinated mediation action in response to an identified environmentalanomaly related to the shipping container transporting at least onenode-enabled battery system and at least one node-enabled package systemfor a battery in accordance with an embodiment of the invention;

FIG. 60A is a diagram illustrating an exemplary multi-node-enabledpackage system for transporting multiple batteries having integratedenvironmental detection and reporting functionalities in accordance withan embodiment of the invention;

FIG. 60B is a diagram illustrating an exemplary multi-node-enabledpackage system for transporting multiple batteries having integratedenvironmental detection and reporting functionalities and a packagemaster node in accordance with an embodiment of the invention;

FIG. 61 is a diagram illustrating an exemplary improved system forcoordinated mediation action in response to an identified environmentalanomaly related to the shipping container transporting an exemplarynode-enabled battery system, an exemplary node-enabled package systemfor a battery, and an exemplary multi-node-enabled package system fortransporting multiple batteries in accordance with an embodiment of theinvention;

FIG. 62 is a diagram illustrating an exemplary system for layeredinitiation of a mediation response to a battery-related environmentalanomaly involving a node-enabled battery apparatus, at least onesecondary sensor-based ID node, and a command node in accordance with anembodiment of the invention;

FIG. 63 is a diagram illustrating an exemplary system for layeredinitiation of a mediation response to a battery-related environmentalanomaly involving multiple node-enabled battery apparatus, at least onesecondary sensor-based ID node, and a command node in accordance with anembodiment of the invention;

FIG. 64 is a diagram illustrating an exemplary system for layeredinitiation of a mediation response to a battery-related environmentalanomaly involving a node-enabled battery apparatus, and a command nodedeployed with multiple environmental sensors in accordance with anembodiment of the invention;

FIG. 65 is a diagram illustrating an exemplary enhanced system fordetecting and verifying an environmental anomaly within an improvedshipping container having primary and secondary command nodes inaccordance with an embodiment of the invention;

FIG. 66 is a flow diagram illustrating an exemplary enhanced method fordetecting and verifying an environmental anomaly related to a shippingcontainer using a first command node mounted to the shipping container,a second command node mounted to the shipping container, and a pluralityof sensor-based ID nodes disposed in different locations within theshipping container in accordance with an embodiment of the invention;

FIG. 67 is a diagram illustrating an exemplary system for securelymonitoring a shipping container for an environmental anomaly usingelements of a wireless node network that interact with an externaltransceiver associated with a transit vehicle having at least temporarycustody of the shipping container in accordance with an embodiment ofthe invention;

FIG. 68 is a flow diagram illustrating an exemplary method for securelymonitoring a shipping container for an environmental anomaly based uponconfirmed sensor-based ID nodes used as trusted sensors in accordancewith an embodiment of the invention;

FIG. 69 is a flow diagram illustrating an exemplary method for securelymonitoring a shipping container for an environmental anomaly based uponconfirmed sensor data used as trusted sensor data in accordance with anembodiment of the invention;

FIG. 70 is a diagram illustrating an exemplary node-enhanced detectionblanket shown in perspective within a cutaway view of a shippingcontainer in accordance with an embodiment of the invention;

FIG. 71 is a diagram illustrating an exemplary system for enhanceddetecting of an environmental anomaly relative to packages maintained ina shipping container using multiple types of node-enabled detectionblankets below and above the packages in accordance with an embodimentof the invention;

FIG. 72 is a diagram illustrating an exemplary rigid type ofnode-enabled detection blanket in accordance with an embodiment of theinvention;

FIG. 73 is a diagram illustrating an exemplary node-enabled detectionblanket having multiple panels in accordance with an embodiment of theinvention;

FIG. 74 is a diagram illustrating an exemplary flexible webbing type ofnode-enabled detection blanket in accordance with an embodiment of theinvention;

FIG. 75 is a diagram illustrating another exemplary system for enhanceddetecting of an environmental anomaly relative to packages maintained ina shipping container using multiple node-enabled detection blanketsdisposed relative to different layers of the packages in accordance withan embodiment of the invention;

FIGS. 76A-76C are a series of diagrams illustrating an exemplaryshipping container having an exemplary base pallet with an exemplarynode-enabled detection blanket attached to the base pallet along withadditional features that may be deployed as part of the exemplarynode-enabled detection blanket in accordance with an embodiment of theinvention;

FIG. 77 is a flow diagram illustrating an exemplary adaptive method formonitoring a shipping container for an environmental anomaly using awireless node network as a command node refines monitoring whendetecting the environmental anomaly in accordance with an embodiment ofthe invention;

FIG. 78 is a diagram illustrating an exemplary system for detecting anenvironmental anomaly related to a shipment package for transport withina shipping container on a transit vehicle having an external transceiverwhere the system includes an exemplary package command node inaccordance with an embodiment of the invention; and

FIGS. 79A-79C are diagrams illustrating an exemplary system fordetecting an environmental anomaly related to a shipment package fortransport within a shipping container on a transit vehicle having anexternal transceiver where the system includes an exemplary packagecommand node that interacts and works with an exemplary shippingcontainer command node in accordance with an embodiment of theinvention.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments. Whereverpossible, the same reference numbers are used in the drawings and thedescription to refer to the same or like parts.

In general, the following describes various embodiments of acontextually aware hierarchical wireless node network that may bemanaged, operated, and applied by principles as set forth herein as partof exemplary systems, apparatus, and methods involved with detectingenvironmental anomalies. In general, exemplary embodiments of thewireless node network may include various interconnected devices. Forexample, there may be one or more lower level devices or nodes (e.g., anID node not having a sensor or a sensor-based ID node) that rely onshorter-range communication with a mid-level device or node (e.g., amaster node capable of self-locating or a command node that may not haveself-location circuitry onboard), which is operative to communicate witha higher level device (e.g., a transceiver that is part of a transitvehicle but disposed external to shipping containers on the vehicle)over a different communication path while the lower and mid-level nodeis unable to communicate directly with the higher level device. In someembodiments of the network, a further higher level device (e.g., aremote control center or remote server) may be in communication with oneor more of the higher level devices (e.g., the external transceiver onthe transit vehicle) below it in the network.

Those skilled in the art will appreciate that such a hierarchy ofdifferent functional communicating network components (generallyreferred to as network devices) may be characterized as a network ofnodes. Those skilled in the art will appreciate that in someembodiments, the wireless node network may include the externaltransceiver and/or remote server as well as different wireless nodesdespite the fact that the external transceiver and/or remote server maynot be a dedicated wireless component. In other embodiments, the networkmay include similar types of wireless nodes or different types ofwireless nodes.

Further, those skilled in the art will appreciate that each embodimentdescribed herein effects improvements to particular technologies, suchas enhancing and improving how to quickly and automatically detect anenvironmental anomaly as well as providing an enhanced method ofinitiating an automatic mediation response to the detected environmentalanomaly that helps avoid damage to property being shipped, vehiclestransporting such property, and helping to avoid loss of life due tosuch an environmental anomaly using an adaptive, context-aware wirelessnode network of node elements. Each embodiment describes a specifictechnological application of one or more nodes that operate in such awireless node network where the specific technological applicationimproves or otherwise enhances such technical fields as explained andsupported by the disclosure that follows.

Those skilled in the art will understand through the following detaileddescription that the nodes may be associated with items, objects, ormaterials (collectively and generally referred to herein as “packages”)or be disposed near such packages and may be used to identify and locatethe packages, detect a surrounding environmental condition near the nodeand/or package while being dynamically programmed during operation ofthe network and while the packages may be loaded, unloaded, and duringtransport alone or within a shipping container (such as a ULD type ofcontainer). The following further describes various embodiments of awireless node network, exemplary ways to monitor and manage componentsof a wireless node network, exemplary ways to better determine thelocation of components of a wireless node network, and applications of awireless node network to enhance logistics operations that rely upon awireless node network that can improve the detection of an environmentalanomaly, provide enhanced layered alerting as part of a mediatedresponse to the detected anomaly, cause or initiate layered types ofmediation responses to such an environmental anomaly, and conduct suchmediation responses in a targeted, selective, and rapid manner so as toimprove the safety of transporting any such packages.

Wireless Node Networks

FIG. 1 illustrates a basic diagram of an exemplary wireless node networkin accordance with an embodiment of the invention. The exemplary networkshown in FIG. 1 comprises a server 100 connected to a network 105, whichis also operatively connected to different network components, such as amaster node 110 a and indirectly to an ID node 120 a through master node110 a. Master node 110 a is typically connected to an ID node 120 a viashort-range wireless communications (e.g., Bluetooth® formattedcommunications). Master node 110 a is typically connected to server 100through network 105 via longer-range wireless communication (e.g.,cellular) and/or medium range wireless communication (e.g., wirelesslocal area data networks or Wi-Fi). ID node 120 a is typically a lowcost device that may be easily placed into a package, be integrated aspart of packaging, or otherwise associated with an item to be trackedand located, such as package 130, a person, or object (e.g., vehicle,etc.). As shown in FIG. 1, an ID node is generally capable ofcommunicating directly with a master node but incapable of communicatingdirectly with the server, while a master node is capable ofcommunicating directly with the server and separately and directlycommunicating with other nodes (such as an ID node or another masternode). Additional exemplary wireless node networks may includeadditional nodes (such as type of master node referred to as a commandnode, and a further network element referred to as an externaltransceiver associated with a transit vehicle). The ability to deploy ahierarchy of nodes within an exemplary wireless node network todistribute tasks and functions at the different levels in an efficientand economical manner helps to facilitate a wide variety of adaptivelocating, tracking, managing, monitoring, detecting, reporting, andmediation responsive applications using such a network of nodes asdiscussed in more detail below.

In general, the lower cost, lower complexity ID node 120 a is managed bythe higher complexity master node 110 a and server 100 as part ofkeeping track of the location of ID node 120 a (and the associateditem), thereby providing intelligent, robust, and broad visibility aboutthe location and status of ID node 120 a. In a typical embodiment, IDnode 120 a is first associated with an item (e.g., package 130, aperson, or object). As ID node 120 a moves with the item, the ID node120 a becomes associated with the master node 110 a, and the server 100is updated with such information. Further movement of the ID node 120 aand item may cause the ID node 120 a to disassociate with master node110 a and be handed off to become associated another master node (notshown), after which the server 100 is again updated. As such, the server100 generally operates to coordinate and manage information related tothe ID node 120 a as the item physically moves from one location toanother. Further details of the architecture and functionality of anembodiment of an exemplary ID node and master node as described below inmore detail with respect to FIGS. 3 and 4, while exemplary server 100 isdescribed below in more detail with respect to FIG. 5.

While server 100 is shown connecting through network 105, those skilledin the art will appreciate that server 100 may have a more direct ordedicated connections to other components illustrated in FIG. 1, such asmaster node 110 a, depending upon implementation details and desiredcommunication paths. Furthermore, those skilled in the art willappreciate that an exemplary server may contain a collection ofinformation in a database (not shown in FIG. 1), while multipledatabases maintained on multiple server platforms or network storageservers may be used in other embodiments to maintain such a collectionof information. Furthermore, those skilled in the art will appreciatethat a database may be implemented with cloud technology thatessentially provides networked storage of collections of informationthat may be directly accessible to devices, such as master node 110 a.

Network 105 may be a general data communication network involving avariety of communication networks or paths. Those skilled in the artwill appreciate that such exemplary networks or paths may be implementedwith hard wired structures (e.g., LAN, WAN, telecommunication lines,telecommunication support structures and telecommunication processingequipment, etc.), wireless structures (e.g., antennas, receivers,modems, routers, repeaters, etc.) and/or a combination of both dependingupon the desired implementation of a network that interconnects server100 and other components shown in FIG. 1 in an embodiment of the presentinvention.

Master node 110 a and ID node 120 a are types of nodes. A node isgenerally an apparatus or device used to perform one or more tasks aspart of a network of components. An embodiment of a node may have aunique identifier, such as a Media Access Control (MAC) address or anaddress assigned to a hardware radio like an Internet Protocol 6 (IPv6)identifier. In some embodiments, the node's unique identifier may becorrelated to a shipment identifier (e.g., a shipment tracking number inone example), or may itself be a shipment's tracking reference.

An ID node, such as ID node 120 a, is generally a low cost activewireless device. In one embodiment, an exemplary ID node is atransceiver-based processing or logic unit having a short-range radiowith variable RF characteristics (e.g., programmable RF output powerrange, programmable receiver sensitivity), memory accessible by theprocessing unit, a timer operatively coupled to the processing unit, anda power source (e.g., a battery) that provides power for the circuitryof the ID node. For example, the physical implementation of an exemplaryID node may be small, and, thus, amenable to integration into a package,label, container, or other type of object. In some implementations of anID node, the node is rechargeable while other implementations do notpermit recharging the power source for the ID node. In otherimplementations, the ID node is environmentally self-contained or sealedso as to enable robust and reliable operations in a variety ofenvironmentally harsh conditions.

A master node, such as master node 110 a, generally serves as anintelligent bridge between the ID node 120 a and the server 100.Accordingly, a master node is generally more sophisticated than an IDnode. In one example embodiment, an exemplary master node is a devicehaving a processing or logic unit, a short-range radio (with may havevariable RF characteristics) used for communicating with other nodes (IDnodes and other master nodes), a medium and/or long-range radio forcommunication with the server 100, memory accessible by the processingunit, a timer operatively coupled to the processing unit, and a powersource (e.g., a battery or a wired power supply connection) thatprovides power for the circuitry of the master node. The exemplarymaster node, such as master node 110 a, may be positioned in a knownfixed location or, alternatively, be a mobile unit having dedicatedlocation positioning circuitry (e.g., GPS circuitry) to allow the masternode to determine its location by itself.

While the embodiment illustrated in FIG. 1 shows only a single masternode and a single ID node, those skilled in the art will appreciate thata wireless network consistent with an embodiment of the invention mayinclude a wide array of similar or different master nodes that eachcommunicate with the server 100 and/or other master nodes, and a widevariety of similar or different ID nodes. Thus, the exemplary networkshown in FIG. 1 is a basic embodiment, while the exemplary network shownin FIG. 2 is a more detailed exemplary wireless node network inaccordance with another embodiment of the invention.

Referring now to FIG. 2, another exemplary wireless node network isshown including server 100 and network 105. Here, master nodes 110 a,110 b, 110 c are deployed and connected to network 105 (and by virtue ofthose respective connections, to server 100) as well as to each other.ID nodes 120 a, 120 b, 120 e are shown as connectable or operative tocommunicate via different paths to various master nodes. However, IDnodes 120 c and 120 d are shown in FIG. 2 connected to ID node 120 b butnot to any of the master nodes. This may be the case if, for example, IDnodes 120 b, 120 c, 120 d are associated with different items (e.g.,packages) within a larger container 210 (or grouped together on apallet). In such an example, only ID node 120 b may remain within thewireless communication range of any master node. This may, for example,be because of the positions of the different ID nodes within thecontainer relative to the closest master node, adverse RF shieldingcaused by the container, adverse RF shielding caused by packaging of theitem, or adverse RF shielding caused by other proximate material thatinterferes with radio transmissions (e.g., several packages of metalitems between the ID node and any master node outside the container).Thus, in the illustrated configuration of the exemplary network shown inFIG. 2, ID nodes 120 c and 120 d may be out of range from the masternodes, yet still have an operative communication path to a master nodethrough ID node 120 b.

Indeed, in one example, prior to placement within container 210, ID node120 b may actually be a master node but the changed RF environment whenplacing it in container 210 may interfere with the master node's abilityto locate itself via location signals (e.g., GPS signals) and cause themaster node to temporarily operate as an ID node while still providingcommunications and data sharing with other ID nodes in container 210.

User access devices 200, 205 are also illustrated in FIG. 2 as beingable to connect to network 105, master nodes, and ID nodes. Generally,user access devices 200 and 205 allow a user to interact with one ormore components of the exemplary wireless node network. In variousembodiments, user access devices 200, 205, may be implemented using adesktop computer, a laptop computer, a tablet (such as an Apple iPad®touchscreen tablet), a personal area network device (such as aBluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 105 with server 100, over a wired or wirelesscommunication path to master node and ID nodes. Thus, an exemplary useraccess device may be a mobile type of device intended to be easily moved(such as a tablet or smartphone), and may be a non-mobile type of deviceintended to be operated from a fixed location (such as a desktopcomputer).

As shown in FIG. 2, user access devices 200, 205 are coupled and incommunication with network 105, but each of them may also be incommunication with each other or other network components in a moredirect manner (e.g., via near field communication (NFC), over aBluetooth® wireless connection, over a Wi-Fi network, dedicated wiredconnection, or other communication path).

In one example, a user access device, such as device 200 or 205, mayfacilitate associating an ID node (such as ID node 120 a) with thetracking number of a package at the start of a shipment process,coordinating with the server 100 to check on the status and/or locationof the package and associated ID node during transit, and possiblyretrieving data from a master node or ID node related to the shippedpackage. Thus, those skilled in the art will appreciate that a useraccess device, such as devices 200, 205, are essentially interactivecommunication platforms by which a user may initiate shipment of anitem, track an item, determine the status and location of an item, andretrieve information about an item.

An exemplary user access device, such as device 200 or 205, may includesufficient hardware and code (e.g., an app or other program code sectionor sections) to operate as a master node or an ID node in variousembodiments as discussed in more detail below. For example, device 200may be implemented as a mobile smartphone and functionally may operateas an exemplary ID node that broadcasts advertising packet messages toother ID nodes or master nodes for association and sharing data withsuch nodes. In another example, device 200 is implemented as a mobilesmartphone and may operate as an exemplary master node that communicatesand associates with ID nodes and other master nodes, as describedherein, and communicates with the server 100. Thus, those skilled in theart will appreciate an exemplary ID node in FIG. 3 and an exemplarymaster node in FIG. 4, and their respective parts, code and programmodules, may be implemented with an appropriately programmed user accessdevice, such as device 200 or 205. Thus, the following description of anexemplary ID node in FIG. 3 and an exemplary master node in FIG. 4 willbe applicable to a user access device operating as an ID node or amaster node, respectively.

ID Node

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention where components of theID node device are shown as disposed within an ID node enclosure forhousing such a device. In general, the node enclosure is used to housethe components of the ID node and may be made from an environmentallyresistant material so as to survive harsh environments resulting from,for example, temperature, pressure, chemical leaks, and/or radiationleaks. However, in some embodiments, the ID node enclosure may be apurposefully selected environmentally sensitive material that breaksdown when exposed to a particular harsh environmental condition (e.g.,breaking down when exposed to a predetermined threshold temperaturecorresponding to a threshold condition indicative of an environmentalanomaly). For example, the ID node enclosure may be made fromtemperature sensitive materials that may expose one or more of the IDnode's main components (e.g., its processor, battery, memory, wirelesstransceiver) when the ID node is deployed in a very high temperatureenvironment. Further, the ID node enclosure may use a temperaturesensitive material with a higher melting point so that failure of the IDnode with that type of enclosure may be indicative of a secondaryenvironmental condition at a predetermined threshold temperature above atemperature corresponding to a threshold condition for the environmentalanomaly. Thus, the type of material used for a particular ID node'senclosure may be selectively chosen as part of apparatus and systemsthat monitor, detect, and respond to environmental anomalies.

As previously described, one embodiment of an ID node includes atransceiver-based processing or logic unit (processor) having ashort-range radio with variable RF characteristics (e.g., programmableRF output power range, programmable receiver sensitivity), memoryaccessible by the processing unit, a timer operatively coupled to theprocessing unit, and a power source (e.g., a battery) that providespower for the circuitry of the ID node. Referring now to the moredetailed embodiment of FIG. 3, exemplary ID node 120 a is shown tocomprise a processing or logic unit 300 coupled to a variable powershort-range communication interface 375, memory storage 315, volatilememory 320, timer 370, and battery 355. Those skilled in the art willappreciate that processing unit 300 is logic, such as a low powerconsumption microcontroller, that generally performs computations ondata and executes operational and application program code and otherprogram modules or sections thereof within the ID node 120 a. As such,exemplary processing unit 300 operates as a transceiver-based processingcore of ID node 120 a.

Those skilled in the art will also appreciate that exemplary ID node 120a is a hardware-based component that may be implemented with a singleprocessor or logic unit, such as unit 300. In one embodiment, processingunit 300 may be implemented with an Intel® 8051 CPU Core and associatedperipheral circuitry as dictated by the needs of the particularapplication. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 300 as well as more complex andsophisticated microprocessors. Additionally, exemplary processing unit300 may be integrated into a single chip transceiver used as a core ofID node 120 a.

The variable power short-range communication interface 375 of ID node120 a is generally a programmable radio and an omni-directional antennacoupled to the processing unit 300. In other embodiments, interface 375may use an antenna with a different antenna profile when directionalitymay be desired. Those skilled in the art will appreciate thatshort-range communication interface 375 may be implemented withhardware, implemented with a combination of hardware and software, aswell as implemented as a software-defined radio (SDR). Examples ofvariable power short-range communication interface 375 may include otherinterfacing hardware or software elements (not shown) for operativelycoupling the device to a specific short-range communication path (e.g.,a Bluetooth® Low Energy (BLE) connection path communicating at 2.4 GHz).

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and/or the RF receiversensitivity may be dynamically and programmatically varied under controlof processing unit 300. In other embodiments, further RF characteristicsof the radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal depending upon a desired implementation and anticipateduse of ID node 120 a. As will be explained in more detail below, someembodiments may use Broadcast Profile having parameters that may beprogrammatically altered or adjusted. In other words, embodiments of IDnode 120 a (or any other ID node) may have programmatically adjustableRF characteristics (such as an adjustable RF output signal power, anadjustable RF receiver sensitivity, the ability to switch to a differentfrequency or frequency band, etc.).

In any of the embodiments described herein, communication interface 375may be implemented as a wireless transceiver-based communicationinterface with both short-range and longer range communicationcapabilities (i.e., may function as both a first and secondcommunication interface as described in the various embodiments herein).This type of wider range communication interface 375 may be implementedusing LPWAN (Low Power Wide Area Network) connectivity, such as LTE 5G,LTE-M, and NB-IOT (NarrowBand IoT). LPWAN, also commonly referred tolow-power wide-area (LPWA) network or just low-power network (LPN), is atype of wide-area network wireless communication format that allows forextended range, low-bandwidth communications for power sensitiveapplication, such as with devices that are battery powered devices(e.g., ID nodes, mobile master nodes, container nodes, command nodes,and the like). Exemplary types of LPWAN may include ultra-narrowband(UNB) technology from Sigfox, random phase multiple access (RPMA)technology from Ingenu, and other long-range WAN protocol (LoRaWAN)technology as promoted by the LoRa Alliance of companies (e.g., IBM,MicroChip, Cisco, Semtech, Singtel, KPN, Bouygues Telecom). LTE-M is acommunication technology that allows a node-based device (such as asensor-based ID node or command node) to directly connect to a Long TermEvolution (4G) cellular network without a gateway and on batteries.NB-IOT is a low-power communication technology that applies a narrowbandapproach to cellular IoT (Internet of Things) communications allowingfor usage of parts of the GSM spectrum bandwidth in unused 200 kHzbands.

The battery 355 for ID node 120 a is a type of power source thatgenerally powers the circuitry implementing ID node 120 a. In oneembodiment, battery 355 may be a rechargeable power source. In otherembodiments, battery 355 may be a non-rechargeable power source intendedto be disposed of after use. In some embodiments of an ID node, thepower source may involve alternative energy generation, such as a solarcell.

The timer 370 for ID node 120 a generally provides one or more timingcircuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where ID node 120 a conservespower by entering a sleep or dormant state for a predetermined timeperiod as part of overall power conservation techniques, timer 370assists processing unit 300 in managing timing operations. Additionally,an embodiment may allow an ID node to share data to synchronizedifferent nodes with respect to timer 370 and a common timing referencebetween nodes and the server.

An embodiment may implement ID node 120 a to optionally include a basicuser interface (UI) 305 indicating status and allowing basic interactionlike start/stop. In one embodiment, the UI 305 may be implemented withstatus lights, such as multi-mode LEDs. Different colors of the lightsmay indicate a different status or mode for the ID node 120 a (e.g., anadvertising mode (broadcasting), a scanning mode (listening), a currentpower status, a battery level status, an association status, an error,as sensed condition (e.g., exceeding a temperature threshold, exceedinga moisture threshold, and the like)). Other embodiments of an ID nodemay implement UI 305 in a more sophisticated manner with a graphicsdisplay or the like where such status or mode information may bedisplayed as well as one or more prompts.

In a further embodiment, an exemplary status light used as part of theUI 305 of an ID node may also indicate a shipment state. In more detail,an exemplary shipment state may include a status of the shipped item ora status of the item's current shipment journey from an origin to adestination.

An embodiment may also implement ID node 120 a to optionally include oneor more sensors 360. In some embodiments, an ID node implemented withone or more sensors 360 may be referred to as a sensor node orsensor-based ID node. Examples of sensor 360 may include one or moreenvironmental sensors (e.g., pressure, movement, light, temperature,humidity, chemical, radiation, magnetic field, altitude, attitude,orientation, acceleration, etc.) and dedicated location sensors (e.g.,GPS sensor, IR sensor, proximity sensor, etc.). Those skilled in the artwill understand that additional types of sensors that measure othercharacteristics are contemplated for use as sensor 360. Additionally,those skilled in the art will understand that a sensor node orsensor-based ID node may include additional program features to managethe detection, collection, storage, sharing, and publication of thecaptured sensor data.

An embodiment may further implement ID node 120 a to optionally includeone or more magnetic switches 365. A magnetic switch 365, such as a reedswitch, generally operates to close or open an electrical path orconnection in response to an applied magnetic field. In other words,magnetic switch 365 is actuated by the presence of a magnetic field orthe removal of a magnetic field. Various applications, as discussed inembodiments described in more detail below, may involve the operation ofID node 120 a having magnetic switch 365.

Consistent with the embodiment shown in FIG. 3, exemplary ID node 120 amay be implemented based upon a Texas Instruments CC2540 Bluetooth® LowEnergy (BLE) System-on-Chip, which includes various peripherals (e.g.,timer circuitry, USB, USART, general-purpose I/O pins, IR interfacecircuitry, DMA circuitry) to operate as an ID node and, if necessary, tointerface with different possible sensors and other circuitry (e.g.,additional logic chips, relays, magnetic switches) that make up the IDnode.

In additional embodiments, one skilled in the art will appreciate thatsimilar functionality in an ID node may be implemented in other types ofhardware. For example, ID node 110 a may be implemented with speciallyoptimized hardware (e.g., a particular application specific integratedcircuit (ASIC) having the same operational control and functionality asnode control and management code, as described below, discrete logic, ora combination of hardware and firmware depending upon requirements ofthe ID node, such as power, processing speed, level of adjustability forthe RF characteristics, number of memory storage units coupled to theprocessor(s), cost, space, etc.

As noted above, ID node 120 a includes memory accessible by theprocessing unit 300. Memory storage 315 and volatile memory 320 are eachoperatively coupled to processing unit 300. Both memory componentsprovide programming and data elements used by processing unit 300. Inthe embodiment shown in FIG. 3, memory storage 315 maintains a varietyof program code (e.g., node control and management code 325) and otherdata elements (e.g., profile data 330, security data 335, associationdata 340, shared data 345, sensor data 350, and the like). Memorystorage 315 is a tangible, non-transient computer readable medium onwhich information (e.g., executable code/modules, node data, sensormeasurements, etc.) may be kept in a non-volatile and non-transitorymanner. Examples of such memory storage 315 may include a hard diskdrive, ROM, flash memory, or other media structure that allows longterm, non-volatile storage of information. In contrast, volatile memory320 is typically a random access memory (RAM) structure used byprocessing unit 300 during operation of the ID node 120 a. Upon power upof ID node 120 a, volatile memory 320 may be populated with anoperational program (such as node control and management code 325) orspecific program modules that help facilitate particular operations ofID node 120 a. And during operation of ID node 120 a, volatile memory320 may also include certain data (e.g., profile data 330, security data335, association data 340, shared data 345, sensor data 350, and thelike) generated as the ID node 120 a executes instructions as programmedor loaded from memory storage 315. However, those skilled in the artwill appreciate that not all data elements illustrated in FIG. 3 mustappear in memory storage 315 and volatile memory 320 at the same time.

Node Control & Management Code

Generally, an embodiment of node control and management code 325 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a node, such asID node 120 a. In an embodiment, the functionality of code 325 may begenerally similar as implemented in different types of nodes, such as amaster node, an ID node, and a sensor node. However, those skilled inthe art will appreciate that while some principles of operation aresimilar between such nodes, other embodiments may implement thefunctionality with some degree of specialization or in a differentmanner depending on the desired application and use of the node. Inother words, node control and management code 325 may also includefurther program code specific for ID node functionality described in theembodiments described in more detail below that use an ID node. As such,the collective code executing on an ID node, such as ID node 120 a (orany of the other implementations of ID nodes as described herein), actsto programmatically configure the ID node beyond that of a genericprocessing device in order to be specially adapted, via such programcode, to be operative to function unconventionally—whether alone withthe specific functionality described herein or as part of a system.

In a general embodiment, exemplary node control and management code 325may generally comprise several programmatic functions or program modulesincluding (1) a node advertise and query (scan) logic manager (alsoreferred to herein as a node communications manager), which manages howand when a node communicates; (2) an information control and exchangemanager, which manages whether and how information may be exchangedbetween nodes; (3) a node power manager, which manages power consumptionand aspects of RF output signal power and/or receiver sensitivity forvariable short-range communications; and (4) an association managerfocusing on how the node associates with other nodes. What follows isdescription of various embodiments of these basic program modules usedby nodes.

Node Communications Manager—Advertising & Scanning

In an exemplary embodiment, the node advertise and query (scan) logicmanager governs how and when a node should advertise (transmit) itsaddress or query (scan) for the address of neighboring nodes.Advertising is generally done with a message, which may have differentinformation in various parts (e.g., headers, fields, flags, etc.). Themessage may be a single or multiple packets.

In the exemplary embodiment, the “advertise” mode (as opposed to “query”or “scan” mode) is a default mode for an ID Node and has the nodebroadcasting or transmitting a message with its address and relatedmetadata regarding the node. For example, in one embodiment, exemplarymetadata may include information such as the RF output power level, areference number, a status flag, a battery level, and a manufacturername for the node.

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with a general embodiment of theinvention. Referring now to FIG. 6, the structure of an exemplaryadvertisement data packet 600 broadcast as a signal or message from anID node, such as ID node 120 a, is shown. Packet 600 appears with anincreasing level of detail showing exemplary metadata and a format thatseparately maintains distinct types of metadata in different parts ofthe packet. Different embodiments may include different types ofmetadata depending on the deployed application of the ID node.

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention. Referring now to FIG. 7, an exemplary advertisement datapacket 700 is illustrated with exemplary metadata including showingsample information such as the RF Output Power level (e.g., “TX PowerLevel”), a reference number (e.g., “‘FDX ID’ (ASCII Short Name)”, astatus flag (e.g., “Status Flag Value (indicates ‘Ack Requested’)”), abattery level (e.g., “Battery Level Value (Indicates 73% charge)”, and amanufacturer name for the node (e.g., “Company Identifier (currentlyundefined for FedEx)”). In one embodiment, those skilled in the art willappreciate that the reference number may be omitted or obfuscated forsecurity purposes.

In one embodiment, an exemplary advertising data packet may include theRF Output power level, as noted above in FIG. 7, to enable one way tohelp identify the type of node doing the broadcasting and the locationof the broadcasting node. However, if the broadcast RF output powerlevel is fixed and known by the node type, only the node type need beidentifiable from an exemplary advertising data packet, such as packet700.

Regarding how a node communicates, an exemplary node may be in one ofseveral different communication modes. A node in an advertising (ortransmit or broadcast) mode is visible to any other node set in a query(or scan or listen) mode. In an embodiment, the frequency and length ofadvertising may be application and power dependent. For example, innormal operations, an exemplary node will generally advertise in aperiodic manner and expect to make an active connection to another nodeat certain intervals without the need for polling or responsiveprompting from another node, which may be dictated by conditions set byserver 100. In an embodiment, such conditions may be set individuallyfor a node by the server or a higher level node in the network.

If an exemplary node has not received acknowledgement for an advertisingpacket within a particular period, it may enter one or more alertstages. For example, if an exemplary node has not receivedacknowledgement from another node for an advertising packet broadcast bythe exemplary node within a particular time period (also generallyreferred to as an Alert Interval), the exemplary node will enter anAlert Stage 1 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 1 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has not received acknowledgement from a master nodefor an advertising packet broadcast by the exemplary node within anothertime period (e.g., a request from the master node to actively connectand a success connection made), it will enter another alert stage, suchas an Alert Stage 2 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 2 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby master nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has data to upload to the backend, it may alsoenter another type of alert stage. In one embodiment, for example, if anexemplary node has sensor data collected by the exemplary node (orreceived from one or more other nodes that have communicated with theexemplary node), and the data needs to be uploaded to server 100, theexemplary node may enter an update alert stage, such as an Alert Stage3. This prompts the exemplary node to issue a follow-up advertisingpacket having one or more parts of it altered to indicate the AlertStage 3 status. In more detail, this exemplary follow-up advertisingpacket may have a different advertising alert header instructing nearbymaster nodes to make a connection with the exemplary node so that thedata (e.g., sensor data 350) may be transmitted from the exemplary node(e.g., ID node 120 a) to a nearby master node (e.g., master node 110 a).The transmitted data may then be stored by the nearby master node assensor data 450 in either or both of the master node's volatile memory420 and memory storage 415. Subsequent to that storage operation, thenearby master node will transfer the data (e.g., sensor data 450) toserver 100.

As illustrated in FIG. 7 and explained in the above description of alertlevel stages, a status flag in a header of an exemplary advertising datapacket is a field used in the association logic in one or moreembodiments. For example, in one embodiment, the existence of a statusflag in the advertising data packet allows a first node to communicateits status to a second node, and for the second node to report thatstatus to the backend server, such as server 100, without an activedirect connection from the first node to the server. In other words, thestatus flag helps facilitate passive interactions between nodes (such aspassive associations).

In a more detailed embodiment, several exemplary status types areestablished with respect to communications with other nodes. Forexample, the exemplary status types may comprise the following:

-   -   Alert Level 0—no issue, operating normal;    -   Alert Level 1—The advertising node is requesting that any        available node acknowledge the receipt of its advertisement        packet;    -   Alert Level 2—The advertising node is requesting that any        available master node acknowledge the receipt of its        advertisement packet;    -   Alert Level 3—Data for Upload—node has captured data available        for upload through a master node; and    -   Synchronize—The advertising node requests to connect with a        device or sensor that can synchronize data (such as timer or        location information).

By broadcasting the status via, for example, a portion of a header in anadvertising data packet, one or more nodes within range of thebroadcasting node can determine the node's status and initiate activeconnections if requested in the status message.

A request for more information from the advertising node may, in someembodiments, come in the form of a SCAN_REQ message. In general, anexemplary SCAN_REQ is a message sent from a scanning (listening) masternode to an advertising node requesting additional information from theadvertising node. In this example, the alert status bit may indicate tothe scanning master node, for example, at an application layer, whetherthe advertising node is in a mode that will or will not accept aSCAN_REQ. In one embodiment, the non-connectable and discoverable modesof node advertising are in compliance with Bluetooth® Low Energy (BLE)standards.

In another embodiment, a node may have further different modes ofoperation while scanning or listening for other nodes. For example, anode's query or scanning mode may be active or passive. When a node isscanning while passive, the node will receive advertising data packets,but will not acknowledge and send SCAN_REQ. However, when a node isscanning while active, the node will receive advertising data packets,and will acknowledge receipt by sending a SCAN_REQ. A more detailedembodiment may provide the passive and active modes of scanning orinquiry in compliance with Bluetooth® Low Energy (BLE) standards.

In an embodiment, an exemplary node is scanning as it listens for otherwireless nodes broadcasting on the short-range radio. Such scanning maybe in the form of monitoring for an unprompted signal broadcast fromother wireless nodes. An exemplary scanning node may capture, forexample, a MAC address of the advertising node, a signal strength of theRF output signal transmitted from the advertising node, and any othermetadata published by the advertising node (e.g., other information inthe advertising data packet). Those skilled in the art will appreciatethat the scope of “listening” when a node is scanning may vary. Forexample, the query may be limited. In other words, the scope of what anode is particularly interested in and for which it is listening may befocused or otherwise limited. In such a case, for example, theinformation collected may be limited to particular information from atargeted population of short-range wireless nodes advertising; but theinformation collection may be considered “open” where information fromany advertising device is collected.

When nodes are advertising or scanning, an embodiment may make furtheruse of status flags and additional modes when advertising or scanning aspart of how nodes communicate and may be managed. In one example, when ascanning (listening) node receives an advertising data packet with thestatus flag indicating an Alert Level 1 or 2 status, and the scanningnode is in “Passive” scanning mode, the node will switch to “Active”scanning mode for some interval. However, when the scanning node in thissituation is already in an “Active” scanning mode, the node will sendthe SCAN_REQ message and receive a SCAN_RSP from the advertising node(e.g., a message providing the additional information requested from theadvertising node). The scanning node will then switch back to a“Passive” scanning mode.

In another example, when an advertising (broadcasting) node receives aSCAN_REQ from a scanning node, the advertising node will consider thatits advertising data packet has been acknowledged. Further, theadvertising node will reset its “Alert” status flag back to an AlertLevel 0 status. This allows the advertising node to effectively receivean acknowledgement to its advertisement without ever making a connectionto the scanning node, which advantageously and significantly saves onpower consumption.

In yet another example, when a scanning node receives an advertisingdata packet with an Alert Level 3 status flag set, the scanning nodewill attempt to make a connection with the advertising device. Once theconnection is made, the advertising device will attempt to upload itsdata to the connected device

Thus, an embodiment of the node advertise and query (scan) logic managerof code 325 may rely upon one or more status flags, advertising modes,scanning modes, as nodes communicate with each other in variousadvantageous manners.

Node Information Control & Exchange Manager

In an exemplary embodiment, the information control and exchange managerpart of node control and management code 325 determines whether and howinformation may be exchanged between nodes. In the exemplary embodiment,the information control and exchange manager establishes different nodeoperational states where information may be changed according to adesired paradigm for the state. In more detail, an embodiment ofinformation control and exchange manager may establish different levelsof information exchange between nodes with a “non-connectableadvertising” state or mode of operation, a “discoverable advertising”state or mode, and a “general advertising” state or mode operation. Whena node is in the “non-connectable advertising” mode, the nodeinformation exchange is limited. For example, the advertising node maybroadcast information that is captured by one or more querying(scanning) nodes, but no two-way exchange of information happens.

When a node is in the “discoverable advertising” mode and a scanningnode is in “Active” mode, the node information exchange in enabled bothways. For example, the advertising node sends the advertising packet,and in response the scanning node sends the SCAN_REQ packet. After theadvertising node receives the SCAN_REQ requesting additionalinformation, the advertising node sends the SCAN_RSP with the requestedinformation. Thus, in the “discoverable advertising” mode there is atwo-way exchange of information, but no active connection is madebetween the two nodes exchanging information.

Finally, for advanced two-way information exchange, an active connectionmay be used between nodes and information may be exchanged both ways toand from different nodes. In a more detailed embodiment, at this levelof two-way information exchange, nodes are first identified and thenauthenticated as part of establishing the active connection. Onceauthenticated and thereafter actively connected to each other, the nodesmay securely share information back and forth. In one example, a sensornode uploading previously captured environmental information to a masternode may be in this mode or state. In another example, an ID nodeuploading the stored results of a node scanning operation to a masternode may be in this mode or state. In yet another example, a master nodesharing a timer and/or location information with corresponding nodes maybe in this mode or state.

Node Power Manager

In an exemplary embodiment, the node power manager part of node controland management code 325 focuses on managing power consumption and theadvantageous use of power (e.g., an adjustable level of RF output signalpower) in a node. In general, nodes are either powered by a battery(such as battery 355 in an ID node), or by an interface (such asbattery/power interface 470 in a master node) to an external powersource. Examples of an external power source may include, in someembodiments, power supplied from an outlet or power connection within afacility, or power generated onboard a conveyance (e.g., automobile,truck, train, aircraft, ship, etc.). Those skilled in the art willappreciate that an interface to an external power source will begenerally referred to as a “wired” power connection, and that node powermanager may be informed whether a node is wired or powered off abattery, such as battery 355. Further embodiments may implement aninterface to an external power source with wireless power transmission,such as via inductive coils.

In one embodiment, a node may manage power used when performing tasks.For example, a node may manage power when determining which node shouldperform a particular task. In more detail, the collective powerconsumption of a group of devices may be managed by electing to employwired nodes, when feasible or desired, to accomplish a particular task,and saving the battery-powered nodes for other less energy burdensome ortaxing tasks. In another embodiment, historic data may inform the systemof the power needed to accomplish a particular task, and the system maymake a determination of which node should accomplish the particular taskbased upon such historic data. In other embodiments, profile data mayalso be used to inform the system of the power needed to accomplish aparticular task (e.g., a sensor profile that describes powerrequirements for operation of a sensor node that gathers sensor dataover a certain period of time and under certain conditions). The systemmay also make a determination of which node should accomplish theparticular task based upon such profile data.

In another example, the exemplary node power manager may manage powerwhen determining how to best to use and adjust power to more accuratelyaccomplish a particular task. In one embodiment, an RF signal outputfrom a node (such as a short-range RF output signal from an ID node) mayperiodically move through a range of output power or simply switchbetween two or more settings that differ in a detectable manner. Asdisclosed in more detail below, the variability and dynamic adjustmentof RF output signal power may allow other nodes (such as one or moremaster nodes) to see each node at the upper range of the RF outputsignal power, and only see nodes physically close to the advertisingnode at the lower range of signal power.

In another example, the exemplary node power manager may cause a changeto a characteristic of its RF output signal power when the node has beenassociated to a physical place or another node by virtue of context data(such as context data 560 and association logic that utilizes that typeof information). In one embodiment, the node may be instructed to changehow often the node communicates and/or a characteristic of its RF outputpower to preserve power.

In yet another example, all advertising nodes may have their respectivenode power managers periodically cause each respective node to broadcastat a maximum RF output signal power level to ensure they still arewithin range of a scanning ID Node or Master Node. Doing so may increasethe chance of being in communication range and allows the individualnodes to be properly located and managed within the network. Thebroadcast duration may be set or dynamically changed to allow pairing tooccur if needed.

Rather than adjust the RF output signal power level, the exemplary nodepower manager may, in some embodiments, adjust the RF receiversensitivity of a node. This allows for an adjustable range of reception(as opposed to merely an adjustable range of broadcast), which maysimilarly be used to manage power and enhance location determinations asdiscussed herein.

In yet another embodiment, a combination approach may be used in whichthe node power manager may concurrently and independently adjust morethan one RF characteristic of a node. For example, an exemplary nodepower manager may adjust an RF output signal power level and also adjustthe RF receiver sensitivity of a node as the node is located andassociated with other nodes. Those skilled in the art will realize thatthis may be especially useful in an area with an unusually denseconcentration of nodes, and a combination of changing RF output signalpower levels

An embodiment of the exemplary node manager may refer to a power profile(e.g., an exemplary type of profile data 330, 430) when adjusting anode's power characteristics (e.g., consumption of power, use of power,output signal frequency, duty cycle of the output put signal, timing,power levels, etc.).

Node Association Manager

In an exemplary embodiment, the node association manager part of nodecontrol and management code 325 focuses on how the nodes associate withother nodes in conjunction and consistent with the server-sideassociation manager in code 525, as discussed in more detail below.Thus, exemplary node association manager, when executing in a node,directs how the node associates (e.g., enters an active connection modeor generates association data reflecting a temporary logical connection)with one or more other nodes with input from the server.

The exemplary node association manager for a node may indicate through aStatus Flag if the node requires an acknowledgement or connection, or ifit has information available for upload to the backend. Thus, while anode may not be associated or actively connected yet to another node, astatus of the node may be inferred from, for example, the statusinformation in the node's broadcast header.

Regarding connections between nodes, there are generally secureconnections and unsecure connections. While an embodiment may allowunsecure connections between one or more sets of nodes, otherembodiments rely upon secure connections or authenticate pairings ofnodes. In one embodiment, for a node to pair with another node, theexemplary node association manager first identifies the nodes to beassociated and transmits an association request to the server. Therequest may include a specific request to pair the nodes and ask for thecorresponding pairing credentials from the server, such as server 100.Such a pairing may be considered a logical pairing of the node, whichmay be tracked by the server 100 (or other nodes in the network, such asa master node, command node, external transceiver, or remote controlcenter located outside of the transit vehicle). The server 100 may havestaged pairing credentials on particular nodes based on informationindicating the nodes would be within wireless proximity and futurepairing may occur. Visibility to the node relationship may have beendetermined through scan-advertising, or 3^(rd) party data such asbarcode scan information indicating the nodes to be within proximitycurrently or at a future state.

As described in more detail below, associating nodes may involve localgeneration of association data (e.g., association data 340, 440, and thelike) that reflects the logical pairing between the associating nodes.As such, the association data may operate as temporal data indicatingthe logical connection between the nodes whether the nodes are actuallycommunicating with each other or not.

When connecting or not connecting to exchange information under theexemplary node information exchange modes described above, nodesgenerally operate in a number of states, which make up an exemplaryadvertise cycle for an exemplary ID node. Such an exemplary advertisecycle for a node is further explained below with reference to FIG. 8 andin conjunction and consistent with the server-side association managerin code 525, as discussed in more detail below.

Airborne Mode Program Module

In one embodiment, node control and management code 325 may also includean airborne mode program module (not shown). In another embodiment, theairborne mode program module may be implemented as a part of the nodepower manager program module of code 325. An exemplary airborne modeprogram module generally operates to manage the output power of the IDnode's variable power short-range communication interface 375 when theID node is operating in an aircraft. Operating a wireless device withinan aircraft may, in some circumstances, have an unintentional impact onother electronic systems on the aircraft. In more detail, an embodimentof the airborne mode program module may operate to transition the IDnode from different states or modes depending upon particular operationsand/or operational conditions of the aircraft. For example, an exemplaryairborne mode program module may operate to transition the ID node fromone state or mode (e.g., a normal mode prior to takeoff, a disabled modeduring takeoff, an airborne mode while aloft, a disabled mode duringdescent, and a normal mode after landing) based upon detectedenvironmental conditions (e.g., pressure, altitude) and/or flight detailinformation associated with the aircraft. In this way, an ID node may beallowed to normally operate when onboard an aircraft, be disabled fromoperating at all in some circumstances, and be able to operate in anaircraft mode that allows sensing and sensor data capture, but that maylimit transmission of an RF output signal to avoid interference with theaircraft's onboard electronics. Further information related to a methodof managing a wireless device (such as an ID node) in an aircraft isdisclosed in greater detail in U.S. patent application Ser. No.12/761,963 entitled “System and Method for Management of WirelessDevices Aboard an Aircraft,” which is hereby incorporated by reference.

Node Data

As previously noted, volatile memory 320 may also include certain data(e.g., profile data 330, security data 335, association data 340, shareddata 345, sensor data, and the like) generated as the ID node 120 aexecutes instructions as programmed or loaded from memory storage 315.In general, data used on a node, such as an ID node, may be receivedfrom other nodes or generated by the node during operations.

In one embodiment, profile data 330 is a type of data that defines ageneral type of behavior for an ID node, such as a Broadcast Profile(discussed in more detail below). In another embodiment where ID node120 a is a BLE device, profile data 330 may include a Bluetooth®compatible profile related to battery service (exposing the state of abattery within a device), proximity between BLE devices, or messagingbetween BLE devices. Thus, exemplary profile data 330 may exist involatile memory 320 and/or memory storage 315 as a type of data thatdefines parameters of node behavior.

In one embodiment, it may be desired to allow secured pairings of nodes.As will be explained in more detail below, as part of secure pairing ofnodes, a request for pairing credentials is generated and sent to server100. Thus, exemplary security data 335 (e.g., PIN data, securitycertificates, keys, etc.) may exist in volatile memory 320 and/or memorystorage 315 as a type of data associated with providing securedrelationships between nodes, such as the requested security credentials.

Association data, such as association data 340, generally identifies aconnected relationship between nodes. Such a connection may be aninteractive exchange type of connection, but other embodiments mayreflect a mere logical connection between the nodes. For example, IDnode 120 a may become associated with the master node 110 a as the IDnode 120 a moves within range of the master node 110 a and after theserver directs the two nodes to associate (with authorization). As aresult, information identifying the relationship between ID node 120 aand master node 110 a may be provided to server 100 and may be provided,as some point, to each of ID node 120 a and master node 110 a. Thus,exemplary association data 340 may exist in volatile memory 320 and/ormemory storage 315 as a type of data identifying associations betweennodes. In another example, ID node 120 a may detect advertising signalsbroadcast from master node 110 a without prompting master node 110 a tobroadcast such signals (e.g., unprompted broadcasts or non-pollingrelated signals from master node 110 a). In this situation, ID node 120a may passively associate with master node 110 a and generateassociation data 340 on ID node 120 a reflecting the logicalrelationship or connection between ID node 120 a and master node 110 adespite a lack of response from the master node 110 a, and suchassociation data may be passed along to server 100 so that the servermay track what nodes are logically associated with ID node 120 a.

Shared data 345 may exist in volatile memory 320 and/or memory storage315 as a type of data exchanged between nodes. For example, context data(such as environmental data) may be a type of shared data 345.

Sensor data 350 may also exist in volatile memory 320 and/or memorystorage 315 as a type of data recorded and collected from an onboardsensor or from another node. For example, sensor data 350 may includetemperature readings from a temperature sensor onboard an ID node and/orhumidity readings from a humidity sensor in another ID node (e.g., fromanother of the ID nodes within container 210 as shown in FIG. 2).

Thus, an ID node (such as node 120 a shown in FIG. 3) is a lower costwireless node that communicates with other ID nodes and master nodes viaa short-range radio with variable RF characteristics, can be associatedwith other nodes, can broadcast to and scan for other nodes, associatedwith other nodes, and store/exchange information with other nodes.

Master Node

A master node, such as master node 110 a shown in more detail in FIG. 4,shares many ID node features but generally expands upon them in order tofunction as a bridge to a higher level network element, such as theserver 100. In general, while an ID node is a type of lower level nodein an exemplary wireless node network, a master node is a type of higherlevel node (also referred to as a mid-level network device). Anexemplary master node may be in a fixed location or otherwisestationary, while other example master nodes may be implemented asmovable and mobile devices. As will be explained further below, one typeof master node may include a command node that may be disposed as partof or attached to a shipping container (such as a ULD container).

Referring now to FIG. 4, exemplary master node 110 a comprises aprocessing or logic unit 400 coupled to a short-range communicationinterface 480, memory storage 415, volatile memory 420, clock/timer 460,and battery/power interface 470. In some embodiments, the short-rangecommunication interface 480 may have variable power characteristics,such as receiver sensitivity and RF output power level. Those skilled inthe art will appreciate that processing unit 400 is logic, such as amicroprocessor or microcontroller, which generally performs computationson data and executes operational and application program code and otherprogram modules within the master node 110 a.

In general, those skilled in the art will appreciate that thedescription of hardware with respect to ID node 110 a in FIG. 4 appliesto the similar hardware and software features appearing in each type ofnode, including a master node. Those skilled in the art will appreciatethat exemplary master node 110 a is a hardware-based component that mayimplement processor 400 with a single processor or logic unit, a morepowerful multi-core processor, or multiple processors depending upon thedesired implementation. In one embodiment, processing unit 400 may beimplemented with a low power microprocessor and associated peripheralcircuitry. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 400 as well as more complex andsophisticated general purpose or dedicated purpose processors.

In yet another embodiment, exemplary processing unit 400 may beimplemented by a low power ARM1176JZ-F application processor used aspart of a single-board computer, such as the Raspberry Pi Computer ModelB-Rev-2. The ARM application processor is embedded within a Broadcom®BCM2835 system-on-chip (SoC) deployed in the Raspberry Pi Computer. Inthis embodiment, the Raspberry Pi Computer device operates as a core ofexemplary master node 110 a and includes a Secure Digital memory cardslot and flash memory card operating as memory storage 415, a 512 MbyteRAM memory storage operating as volatile memory 420, an operating system(such as Linux) stored on memory storage 415 and running in volatilememory 420, and peripherals that implement clock/timer 460, and a powersupply operating as a power interface 470.

Like short-range interface 375 in ID node 120 a, exemplary master node110 a includes a short-range communication interface 480 as aprogrammable radio and an omni-directional antenna coupled to theprocessing unit 400. In some embodiments, the short-range communicationinterface 480 may have variable RF power characteristics, such asreceiver sensitivity and/or RF output signal power level. In someembodiments, interface 480 may use an antenna with a different antennaprofile when directionality may be desired. Those skilled in the artwill appreciate that short-range communication interface 480 (like thatdescribed above regarding interface 375) may be implemented withhardware, implemented with a combination of hardware and software, aswell as implemented as a software-defined radio (SDR). Examples ofshort-range communication interface 480 may include other hardware (notshown) for operatively coupling the device to a specific short-rangecommunication path (e.g., a Bluetooth® Low Energy (BLE) connection pathcommunicating at 2.4 GHz). While BLE is used in one embodiment to enablea short-range communication protocol, variable power short-rangeinterface 480 may be implemented with other low power, short-rangecommunication protocols, such as ultra-low power communication protocolsused with ultra-wideband impulse radio communications, ZigBee protocols,IEEE 802.15.4 standard communication protocols, and the like.

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and the RF receiver sensitivitymay be dynamically and programmatically varied under control ofprocessing unit 400. In other embodiments, further RF characteristics ofthe radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal as needed depending upon a desired implementation andanticipated use of exemplary master node 110 a. In other words,embodiments of master node 110 a (or any other master node) may haveprogrammatically adjustable RF characteristics (such as an adjustable RFoutput signal power, an adjustable RF receiver sensitivity, the abilityto switch to a different frequency or frequency band, etc.).

In addition to the short-range communication interface 480, exemplarymaster node 110 a includes a medium and/or long-range communicationinterface 485 to provide a communication path to server 100 via network105. Those skilled in the art will appreciate that in some embodiments,an exemplary communication interface deployed may be considered toembody a short-range communication interface (such as interface 480) ora medium/long range communication interface (such as interface 485).However, in more general embodiments, reference to a communicationinterface may include an interface that collectively implements aplurality of different exemplary data communication interfaces whilestill being generally referenced as “a communication interface” or“wireless communication interface.” Furthermore, those skilled in theart will appreciate that communication interface 485 may be implementedwith hardware, implemented with a combination of hardware and software,as well as implemented as a software-defined radio (SDR).

In more detail, an exemplary embodiment of communication interface 485may be implemented with a medium range radio in the form of an IEEE802.11g compliant Wi-Fi transceiver. In another embodiment,communication interface 485 may be implemented with a longer range radioin the form of a cellular radio. In yet another embodiment, both a Wi-Fitransceiver and a cellular radio may be used when best available oraccording to a priority (e.g., first attempt to use the Wi-Fitransceiver if available due to possible lower costs; and if not, thenrely on the cellular radio). In other words, an embodiment may rely uponthe longer range cellular radio part of interface 485 as an alternativeto the medium range Wi-Fi transceiver radio, or when the medium rangeradio is out of reach from a connecting infrastructure radio withinnetwork 105. In a further embodiment, interface 485 may be implementedas a module providing general purpose signal processing at its core aspart of a software-defined radio, which provides flexibility intransmission techniques, software-defined antennas, and adaptive radioprotocols that may be dynamically changed to implement different mediumand longer range interfaces. Thus, in these embodiments, medium and/orlong-range communication interface 485 may be used to communicatecaptured node information (e.g., profile data 430, association data 440,shared data 445, sensor data 450, and location data 455) to server 100.

In any of the embodiments described herein, communication interfaces 480and 485 may be implemented as a single wireless transceiver-basedcommunication interface with both short-range and longer rangecommunication capabilities (i.e., may function as both a first andsecond communication interface as described in the various embodimentsherein). This type of wider range communication interface may beimplemented using LPWAN (Low Power Wide Area Network) connectivity, suchas LTE 5G, LTE-M, and NB-IOT (NarrowBand IoT). LPWAN, also commonlyreferred to low-power wide-area (LPWA) network or just low-power network(LPN), is a type of wide-area network wireless communication format thatallows for extended range, low-bandwidth communications for powersensitive application, such as with devices that are battery powereddevices (e.g., ID nodes, mobile master nodes, container nodes, commandnodes, and the like). Exemplary types of LPWAN may includeultra-narrowband (UNB) technology from Sigfox, random phase multipleaccess (RPMA) technology from Ingenu, and other long-range WAN protocol(LoRaWAN) technology as promoted by the LoRa Alliance of companies(e.g., IBM, MicroChip, Cisco, Semtech, Singtel, KPN, Bouygues Telecom).LTE-M is a communication technology that allows a node-based device(such as a sensor-based ID node or command node) to directly connect toa Long Term Evolution (4G) cellular network without a gateway and onbatteries. NB-IOT is a low-power communication technology that applies anarrowband approach to cellular IoT (Internet of Things) communicationsallowing for usage of parts of the GSM spectrum bandwidth in unused 200kHz bands.

The battery/power interface 470 for master node 110 a generally powersthe circuitry implementing master node 110 a. In one embodiment,battery/power interface 470 may be a rechargeable power source. Forexample, a master node may have a rechargeable power source along with asolar panel that charges the power source in order to help facilitatedeployment of the master in a remote location. In another embodiment,battery/power interface 470 may be a non-rechargeable power sourceintended to be disposed of after use. In yet another embodiment,battery/power interface 470 may be a power interface connector (such asa power cord and internal power supply on master node 110 a). Thus, whenan exemplary master node is in a fixed or stationary configuration, itmay be powered by a power cord connected to an electrical outlet, whichis coupled to an external power source. However, other mobile masternodes may use an internal power source, such as a battery.

The clock/timer 460 for master node 110 a generally provides one or moretiming circuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where master node 110 aconserves power by entering a sleep or dormant state for a predeterminedtime period as part of overall power conservation techniques,clock/timer 460 assists processing unit 400 in managing timingoperations.

Optionally, an embodiment may also implement master node 110 a asincluding one or more sensors 465 (similar to sensors deployed on IDnode based Sensor nodes and described above with respect to FIG. 3).Additionally, an embodiment of master node 110 a may also provide a userinterface 405 to indicate status and allow basic interaction for reviewof captured node data and interaction with nodes and server 100. In oneembodiment, user interface 405 may provide a display, interactivebuttons or soft keys, and a pointing device to facilitate interactionwith the display. In a further embodiment, a data entry device may alsobe used as part of the user interface 405. In other embodiments, userinterface 405 may take the form of one or more lights (e.g., statuslights), audible input and output devices (e.g., a microphone andspeaker), or touchscreen.

As previously noted, an exemplary master node, such as master node 110a, may be positioned in a known fixed location or, alternatively,includes dedicated location positioning circuitry 475 (e.g., GPScircuitry) to allow the master node self-determine its location or todetermine its location by itself. In other embodiments, alternativecircuitry and techniques may be relied upon for location circuitry 475(rather than GPS), such as location circuitry compatible with othersatellite-based systems (e.g., the European Galileo system, the RussianGLONASS system, the Chinese Compass system), terrestrial radio-basedpositioning systems (e.g., cell phone tower-based or Wi-Fi-basedsystems), infrared positioning systems, visible light based positioningsystems, and ultrasound-based positioning systems).

Regarding memory storage 415 and volatile memory 420, both areoperatively coupled to processing unit 400 in exemplary master node 110a. Both memory components provide program elements used by processingunit 400 and maintain and store data elements accessible to processingunit 400 (similar to the possible data elements stored in memory storage315 and volatile memory 320 for exemplary ID node 120 a).

In the embodiment shown in FIG. 4, memory storage 415 maintains avariety of executable program code (e.g., master control and managementcode 425), data similar to that kept in an ID node's memory storage 315(e.g., profile data 430, security data 435, association data 440, shareddata 445, sensor data 450, and the like) as well as other data morespecific to the operation of master node 110 a (e.g., location data 455that is related to the location of a particular node). Like memorystorage 315, memory storage 415 is a tangible, non-transient computerreadable medium on which information (e.g., executable code/modules,node data, sensor measurements, etc.) may be kept in a non-volatile andnon-transitory manner.

Like volatile memory 320 in ID node 120 a, volatile memory 420 istypically a random access memory (RAM) structure used by processing unit400 during operation of the master node 110 a. Upon power up of masternode 110 a, volatile memory 120 may be populated with an operationalprogram (such as master control and management code 425) or specificprogram modules that help facilitate particular operations of masternode 110 a. And during operation of master 110 a, volatile memory 420may also include certain data (e.g., profile data 430, security data435, association data 440, shared data 445, sensor data 450, and thelike) generated as the master node 110 a executes instructions asprogrammed or loaded from memory storage 415.

Master Control & Management Code

Generally, an embodiment of master control and management code 425 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a master node,such as master node 110 a. In other words, master control and managementcode 425 may also include further program code specific for master nodefunctionality described in the embodiments described in more detailbelow that use a master node (e.g., a command node 26000 or command node24160 implemented with a master node). As such, the collective codeexecuting on a master node, such as master node 110 a (or any of theother implementations of a master node or command node as describedherein), acts to programmatically configure the master or command nodebeyond that of a generic processing device in order to be speciallyadapted, via such program code, to be operative to functionunconventionally—whether alone with the specific functionality describedherein or as part of a system.

In one embodiment, master control and management code 425 generallycomprises several programmatic functions or program modules including(1) a node advertise and query (scan) logic manager, which manages howand when a node communicates; (2) an information control and exchangemanager, which manages whether and how information may be exchangedbetween nodes; (3) a node power manager, which manages power consumptionand aspects of RF output signal power and/or receiver sensitivity forvariable short-range communications; (4) an association manager focusingon how the node associates with other nodes; and (5) a locationaware/capture module to determine node location.

Master Node Program Modules and ID Node Modules

In an exemplary embodiment, program modules (1)-(4) of master nodecontrol and management code 425 generally align with the functionalityof similarly named program modules (1)-(4) of node control andmanagement code 325 as described above with respect to FIG. 3.Additionally, as node control and management code 325 may also comprisean airborne mode program module, those skilled in the art willappreciate and understand that master node control and management code425 may also comprise a similar functionality airborne mode programmodule in order to allow advantageous operations of a master node whileairborne. However, and consistent with examples set forth below, suchmodules may have some differences when in a master node compared withthose controlling an ID node.

Location Aware/Capture Module

In addition to exemplary program modules (1)-(4) of code 425, anexemplary embodiment of master node control and management code 425 willfurther comprise an exemplary location aware/capture module related tonode location (more generally referred to as a location manager modulefor a master node). In general, the exemplary location aware/capturemodule deployed in an exemplary master node may determine its ownlocation and, in some embodiments, the location of a connected node.Embodiments of the exemplary location aware/capture module may work inconjunction with location manager program code residing and operating ina server (e.g., as part of server control and management code 525) whendetermining node locations of other nodes, as discussed in more detailherein.

In one embodiment, a master node may be positioned in a known, fixedlocation. In such an embodiment, the exemplary location aware/capturemodule may be aware that the master node location is a known, fixedlocation, which may be defined in a fixed, preset, or preprogrammed partof memory storage 415 (e.g., information in the location data 455maintained in memory storage 415). Examples of such location informationmay include conventional location coordinates or other descriptivespecifics that identify the location of the master node. In anotherembodiment where the master node may not be inherently known or a fixedlocation at all times (e.g., for a mobile master node), the exemplarylocation aware/capture module may communicate with location circuitry,such as GPS circuitry 475 on a master node, to determine the currentlocation of the master node.

In an embodiment, the location of the master node may be communicated tothe server, which may use this location information as part of managingand tracking nodes in the wireless node network. For example, if anexemplary master node is mobile and has determined a new currentlocation using location circuitry 475, the master node may provide thatnew current location for the master node to the server. Additionally,when the master node's exemplary location aware/capture moduledetermines the location of a node associated with the master node, themaster node may also provide the location of that node associated withthe master node to the server.

Server

While FIGS. 3 and 4 illustrate details of hardware and software aspectsof an exemplary ID node and exemplary master node, respectively, FIG. 5provides a more detailed diagram of an exemplary server that may operateas part of an exemplary wireless node network in accordance with anembodiment of the invention. In an exemplary embodiment, server 100 maybe referred to as an Association and Data Management Server (ADMS) thatmanages the nodes, collects information from the nodes, stores thecollected information from the nodes, maintains or has access to contextdata related to the environment in which the nodes are operating, andmay provide information about the nodes (e.g., status, sensorinformation, etc.) to requesting entities. Further details on variousembodiments that take advantage of this functionality are explainedbelow. Those skilled in the art will appreciate that node density,geographic installation characterization, and network connectively areall types of examples of factors that may impact a final architecturedesired for an embodiment of a wireless node network.

Referring now to FIG. 5, exemplary server 100 is shown as a networkedcomputing platform capable of connecting to and interacting with atleast the wireless master nodes. In other embodiments, exemplary server100 is also capable of connecting to and interacting with one or moreuser access devices. Those skilled in the art will appreciate thatexemplary server 100 is a hardware-based component that may beimplemented in a wide variety of ways. For example, server 100 may use asingle processor or may be implemented as one or more part of amulti-processor component that communicates with devices (such as useraccess devices 200, 205) and wireless nodes (such as master node 110 a).

In general, those skilled in the art will further appreciate that server100 may be implemented as a single computing system, a distributedserver (e.g., separate servers for separate server related tasks), ahierarchical server (e.g., a server implemented with multiple levelswhere information may be maintained at different levels and tasksperformed at different levels depending on implementation), or a serverfarm that logically allows multiple distinct components to function asone server computing platform device from the perspective of a clientdevice (e.g., devices 200, 205 or master node 110 a). In some regionaldeployments, an exemplary server may include servers dedicated forspecific geographic regions as information collected within differentregions may include and be subject to different regulatory controls andrequirements implemented on respective regional servers.

Likewise, while the embodiment shown in FIG. 5 illustrates a singlememory storage 515, exemplary server 100 may deploy more than one memorystorage media. And memory storage media may be in differingnon-transitory forms (e.g., conventional hard disk drives, solid statememory such as flash memory, optical drives, RAID systems, cloud storageconfigured memory, network storage appliances, etc.).

At its core, exemplary server 100 shown in FIG. 5 comprises a processingor logic unit 500 coupled to a network interface 590, which facilitatesand enables operative connections and communications through network 105with one or more master nodes as well as, in some embodiments, useraccess devices, such as devices 200, 205. In one embodiment, server 100may include a medium and/or long-range communication interface 595 withwhich to more directly communicate with one or more master nodes. Usingthese communication paths as well as program code or program modules(such as server control and management code 525), the server 100generally operates to coordinate and manage information related to an IDnode as an item associated with the ID node physically moves from onelocation to another.

As a computing platform, the processing unit 500 of exemplary server 100is operatively coupled to memory storage 515 and volatile memory 520,which collectively store and provide a variety of executable programcode (e.g., server control and management code 525), data similar tothat kept in a master or ID node's respective memory storage (e.g.,profile data 530, security data 535, association data 540, shared data545, sensor data 550, location data 555) and context data 560 related tothe environment in which the nodes are operating (e.g., informationgenerated from within the wireless node network and information createdexternal to the wireless node network).

Like memory storage 315 and storage 415, memory storage 515 is atangible, non-transient computer readable medium on which information(e.g., executable code/modules (e.g., server control and management code525), node-related data (e.g., profile data 530, security data 535,association data 540, location data 555, etc.), measurement information(e.g., a type of shared data 545, sensor data 550, etc.), andinformation on the contextual environment for the nodes (e.g., contextdata 560) may be kept in a non-volatile and non-transitory manner.

Those skilled in the art will appreciate that the above identificationof particular program code and data are not exhaustive and thatembodiments may include further executable program code or modules aswell as other data relevant to operations of a processing-based device,such as an ID node, a master node, and a server.

Context Data

As noted above, server 100 may access context data 560 as part ofmanaging nodes in the wireless node network. The exemplary server 100may contain a collection of such context data 560 in a context database565 according to an embodiment. As illustrated in FIG. 5, exemplarycontext database 565 is a single database accessible by processing unit500 internal to server 100. Those skilled in the art will readilyunderstand that other configurations that provide an accessiblecollection of context data 560 are possible and contemplated within thescope and principles of embodiments of the invention. For example,context database 565 may be an externally accessible database (ormultiple databases), such as an accessible storage maintained outsidethe server 100 via a dedicated interface or a network storage device (ornetwork attached storage (NAS) unit). In yet another embodiment, thecontext database may be separately maintained by an external databaseserver (not shown) that is distinct from server 100, but accessiblethrough a communication path from server 100 to a separate databaseserver (e.g., via network 105). Furthermore, those skilled in the artwill appreciate that context database 565 may be implemented with cloudtechnology that essentially provides a distributed networked storage ofcollections of information (such as context data 560, sensor data 550,shared data 545, etc.) accessible to server 100.

Within context database 565, an exemplary embodiment of the collectionof context data 560 may be maintained that generally relates to anenvironment in which the nodes are operating or anticipated to beoperating. In more detail, the context data 560 may generally relate towhat a similar node has experienced in a similar environment to what agiven node is presently experiencing or is anticipated to experience asthe given node moves.

In a general example, an environment in which a node may be actually oranticipated to be operating may include different types ofenvironments—for example, an electronic communication environment (e.g.,an RF environment that may be cluttered with signals or includematerials or structure that may impede or otherwise shield RFcommunications), a physical environment of an anticipated path alongwith the identified node moves (e.g., temperature, humidity, security,and other physical characteristics), a conveyance environment related tohow a node may move or be anticipated to be moving (e.g., speed andother parameters of a truck, aircraft, conveyor system), and a densityenvironment related to the density of nodes within an area near aparticular node (e.g., how many nodes are anticipated to occupy acorridor, such as structure 2200 shown in FIG. 22A, or a storagefacility through which a particular ID node is anticipated to transit onits shipping path).

In light of these different aspects of a node's operating environment,exemplary context data 560 may provide information related to differentstructures and conditions related to movement of an item (e.g., aparticular type of courier device, vehicle, facility, transportationcontainer, etc.). Such information may be generated by an entityoperating the wireless node network, such as a shipping company.Additionally, exemplary context data 560 may include third party datagenerated external to the wireless node network. Thus, context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention.

In general, FIG. 5 illustrates exemplary types of context data 560 beingmaintained in database 565 and in volatile memory 520. Those skilled inthe art will appreciate that context data 560 may also be maintained inother data structures, in addition to or instead of maintaining suchinformation in a database. As illustrated in FIG. 5, exemplary types ofcontext data 560 may include but are not limited to scan data 570,historic data 575, shipment data 580, layout data 585, RF data 587, and3^(rd) party data.

Scan data 570 is generally data collected for a particular item relatedto an event. For example, when an item is placed in a package (such aspackage 130), a label may be generated and placed on the exterior of thepackage. The label may include a visual identifier that, when scanned byan appropriate scanning device capable of capturing, identifies thepackage. The information generated in response to scanning theidentifier (a type of event), may be considered a type of scan data.Other scan data 570 may include, for example, general inventory datagenerated upon manual entry of information related to the package;captured package custodial control data; and bar code scan data.

Historic data 575 is generally data previously collected and/or analyzedrelated to a common characteristic. Historic data 575 embodiesoperational knowledge and know-how for a particular characteristicrelevant to operations of the wireless node network. For example, thecommon characteristic may be a particular event (e.g., movement of anitem from an open air environment to within a particular closedenvironment, such as a building), a type of item (e.g., a type ofpackage, a type of content being shipped, a location, a shipment path,etc.), a success rate with a particular item (e.g., successfulshipment), and the like. Another example of historic data 575 mayinclude processing information associated with how an item has beenhistorically processed as it is moved from one location to another(e.g., when moving within a particular facility, processing informationmay indicate the item is on a particular conveyor and may includeinformation about the conveyor (such as speed and how long it isanticipated the item will be on the conveyor)).

Shipment data 580 is generally data related to an item being moved fromone location to another location. In one embodiment, shipment data 580may comprise a tracking number, content information for an item beingshipped, address information related to an origin and destinationlocations, and other characteristics of the item being moved.

Layout data 585 is generally data related to the physical area of one ormore parts of an anticipated path. For example, an embodiment of layoutdata 585 may include building schematics and physical dimensions ofportions of a building in which a node may be transiting. An embodimentmay further include density information associated with physical areasto be transited and anticipated numbers of potential nodes in thoseareas as types of layout data. In another example, an embodiment oflayout data may include a configuration of how a group of packages maybe assembled on a pallet, placed into a shipping container (e.g., a unitload device (ULD)) that helps move a collection of items on variousforms with single mode or intermodal transport.

RF data 587 is generally signal degradation information about a signalpath environment for a particular type of node and may relate toparticular adverse RF conditions that may cause signal fluctuations,interference, or other degradation from the otherwise optimal signalpath environment for that type of node. For example, RF data may includeshielding effects when using a particular packaging or location,shielding effects when the package is within a particular type ofcontainer or assembled as part of a palletized shipment, shieldingeffects when particular content is shipped, and other physical andelectronic interference factors.

Third party data 589 is an additional type of context data 560 thatgenerally includes data generated outside the network. For example,third party data may include weather information associated withparticular areas to be transited as the item is moved along ananticipated path from one location to another. Those skilled in the artwill appreciate other types of third party data that relate to physicaland environmental conditions to be faced by an item being moved from onelocation to another may also be considered context data 560.

The use of context data, such as context data 560 described above,advantageously helps server 100 better manage movement of items, providebetter location determination, enhance intelligent operation andmanagement of different levels of the wireless node network, and provideenhanced visibility to the current location and status of the itemduring operation of the wireless node network. In one embodiment, servercontrol and management code 525 may provide such functionality thatenables the wireless node network to be contextually aware andresponsive.

Server Control & Management Code

Generally, server control and management code 525 controls operations ofexemplary server 100. In an embodiment, server control and managementcode 525 is a collection of software features implemented asprogrammatic functions in code or separate program modules thatgenerally control the behavior of server 100. Thus, exemplary servercontrol and management code 525 may be implemented with severalprogrammatic functions or program modules including, but not limited to,(1) a server-side association manager, which provides a framework formore robust and intelligent management of nodes in the wireless nodenetwork; (2) a context-based node manager, which enhances management ofnodes in the wireless node network based upon context data; (3) asecurity manager, which manages secure pairing aspects of nodemanagement; (4) a node update manager, which provides updated ordifferent programming for a particular node and shares information withnodes; (5) a location manager for determining and tracking the locationof nodes in the network; and (6) an information update manager, whichservices requests for information related to the current status of anode or generally providing information about a node or collected from anode.

Server-Side Association Manager

The server-side association manager (also referred to as a server-sideassociation management function) is generally a program module inexemplary code 525 that is responsible for intelligently managing thenodes in the wireless node network using a secure information framework.In an embodiment, this framework may be implemented to be acontext-driven, learning sensor platform. The framework may also enablea way for information (such as RF scan, location, date/time, and sensordata) to be securely shared across nodes, a way to change the behaviorof a node, and for a node to know it is considered “missing.” Theframework established during operation of the server-side associationmanager allows the network of nodes to be managed as a system withenhanced and optimized accuracy of determining the physical location ofeach ID Node. Further information regarding particular embodiments ofsuch an association management framework and methods are explained belowin more detail.

Context-Based Association Manager

The context-based node manager is generally a program module inexemplary code 525 that is responsible for incorporating context data aspart of management operations to provide an enhanced data foundationupon which visibility of the nodes may be provided. In some embodiments,the context-based node manager may be implemented as part of theserver-side association manager while other embodiments may implementthe context-based node manager as a separate program module.

In one embodiment, the enhanced data foundation relies upon contextdata, such as context data 560 (e.g., scan data 570, historic data 575,shipment data 580, layout data 585, and other third party contextualdata providing information regarding the conditions and environmentsurrounding an item and ID node moving from one location to another.Such context data (e.g., the network know-how, building layouts, andoperational knowledge of nodes and shipping paths used with the wirelessnode network) may provide the enhanced building blocks that allow theserver 100 to manage tracking and locating of nodes in a robustlyenriched contextual environment. In an embodiment, context-basedmanagement provides visibility to the system through data analysis forwhen and how associations should be expected as the nodes travel throughthe wireless node network. In other embodiments, it may provide thefoundation for better understanding RF signal degradation, which can becaused by the operating environment, packaging, package content, and/orother packages related to an item and its ID node.

Security Manager

The security manager module, which may be implemented separately or aspart of the association manager module in exemplary server control andmanagement code 525, helps with associating two nodes in the wirelessnode network by managing aspects of secure pairing of the nodes. In oneembodiment, security manager module provides the appropriate pairingcredentials to allow a node to securely connect to another node. Thus,when a node desires to connect to another node, an embodiment requiresappropriate pairing credentials be generated by the server, provided tothe nodes, and observed within the nodes to allow for a successfulconnection or association of nodes.

In operation, a node (such as master node 110 a) identifies the addressof the node (such as ID node 120 a) to whom it desires to connect. Withthis address, the node prepares a pairing request and sends the requestto the server 110. The server 100 operates under the control of thesecurity manager module of the association manager, and determineswhether the requesting node should be connected or otherwise associatedwith the other node. If not, the server does not issue the requestedsecurity credentials. If so and in accordance with the desiredassociation management paradigm set by the association manager of code525, server provides the requested credentials necessary for asuccessful wireless pairing and the establishment of securecommunications between the associated nodes.

Node Update Manager

The exemplary server control and management code 525 may include a nodeupdate manager module that provides updated programming information tonodes within the wireless node network and collects information fromsuch nodes (e.g., shared data 545, sensor data 550). The node updatemodule may be implemented separately or as part of the associationmanager module in exemplary server control and management code 525.

Providing an update to a node's programming may facilitate and enabledistribution of node functions to save power and better manage the nodesas a system. For example, one embodiment may alter the functionalresponsibility of different nodes depending on the context orassociation situation by temporarily offloading responsibility for aparticular function from one node to another node. Typically, the serverdirects other nodes to change functional responsibility. However, insome embodiments, a master node may direct other nodes to alterfunctional responsibility.

Sharing information between nodes and with server (e.g., via anexemplary node update manager) facilitates collecting information from anode and sharing information with other nodes as part of an associationmanagement function of server 100. For example, one embodiment maycollect and share RF scan data (a type of shared data 545), informationabout a node's location (a type of location data 555), systeminformation about date/time (another type of shared data 545), andsensor measurements collected from sensor nodes (a type of sensor data550).

Location Manager

The exemplary server control and management code 525 may include alocation manager module that helps determine and track node locations.In a general embodiment, the location of a node may be determined by thenode itself (e.g., a master node's ability to determine its own locationvia location circuitry 475), by a node associated with that node (e.g.,where a master node may determine the location of an ID node), by theserver itself (e.g., using location information determined by one ormore techniques implemented as part of code 525), and by a combinedeffort of a master node and the server.

In general, an exemplary ID node may be directly or indirectly dependenton a master node to determine its actual physical location. Embodimentsmay use one or more methodologies to determine node location. Forexample and as more specifically described below, possible methods fordetermining node location may relate to controlling an RF characteristicof a node (e.g., an RF output signal level and/or RF receiversensitivity level), determining relative proximity, consideringassociation information, considering location adjustments for contextinformation and an RF environment, chaining triangulation, as well ashierarchical and adaptive methods that combine various locationmethodologies. Further information and examples of how an exemplarylocation manager module may determine a node's location in accordancewith such exemplary techniques are provided in more detail below.

Additionally, those skilled in the art will appreciate that it may alsobe possible to determine what constitutes an actionable location versusactual location based upon contextual information about the item beingtracked. For example, a larger item may require relatively less locationaccuracy than a small item such that operational decisions and statusupdates may be easier implemented with knowledge of context. If the sizeof the item is known, the location accuracy can be tuned accordingly.Thus, if a larger item is to be tracked, or if the system's contextualawareness of it is such that lower location accuracy can be used, astronger signal and thus wider area of scanning may be employed, whichmay help in situations where RF interference or shielding is an issue.

Information Update Manager

The exemplary server control and management code 525 may include aninformation update manager module that provides information related tooperations of the wireless node network and status of nodes. Suchinformation may be provided in response to a request from a deviceoutside the wireless node network (such as user access device 200). Forexample, someone shipping an item may inquire about the current statusof the item via their laptop or smartphone (types of user accessdevices), which would connect to server 100 and request suchinformation. In response, the information update manager module mayservice such a request by determining which node is associated with theitem, gathering status information related to the item (e.g., locationdata, etc.), and provide the requested information in a form that istargeted, timely, and useful to the inquiring entity.

In another example, a user access device may connect to server 100 andrequest particular sensor data from a particular node. In response,information update manager may coordinate with node update manager, andprovide the gathered sensor data 545 as requested to the user accessdevice.

Node Filtering Manager

An embodiment of exemplary server control and management code 525 mayoptionally comprise a node filtering manager, which helps manage thetraffic of nodes with a multi-level filtering mechanism. The filteringessentially sets up rules that limit potential associations andcommunications. An example of such a node filtering management maydefine different levels or modes of filtering for a master node (e.g.,which ID nodes can be managed by a master node as a way of limiting thecommunication and management burdens on a master node).

In one example, a “local” mode may be defined where the ID node onlycommunicates and is managed by the assigned master node at the locationwhere the last wireless node contact back to server 100 and/or wherethird party data indicates the assigned master node and ID node are inphysical and wireless proximity. Thus, for the “local” mode of trafficfiltering, only the assigned master node communicates and processesinformation from a proximately close and assigned ID node.

Moving up to a less restrictive filtering mode, a “regional” mode offiltering may be defined where the ID node may communicate and bemanaged by any master node at the location last reported back to server100 and/or where third party data indicates the ID node is located.Thus, for the “regional” mode of traffic filtering, any master node nearthe ID node may communicate and process information from that ID node.This may be useful, for example, when desiring to implement a limit onassociations and pairings to within a particular facility.

At the least restrictive filtering mode, a “global” mode of filteringmay be defined as essentially system-wide communication where the IDnode may be allowed to communicate and be managed by any master node. Inother words, the “global” mode of traffic filtering allows any ID nodewithin the wireless node network to communicate information through aparticular master node near the ID node may communicate and processinformation from that ID node.

Thus, with such exemplary filtering modes, an ID node in a certaincondition (e.g., distress, adverse environmental conditions, adverseconditions of the node, etc.) may signal the need to bypass anyfiltering mechanism in place that helps manage communications andassociation by using the “Alert” Status Flag. In such an example, thiswould operate to override any filtering rules set at the Master Nodelevel in order to allow an ID node to be “found” and connect to anothernode.

Thus, exemplary server 100 is operative, when executing code 525 andhaving access to the types of data described above, to manage the nodes,collect information from the nodes, store the collected information fromthe nodes, maintain or have access to context data related to theenvironment in which the nodes are operating, and provide informationabout the nodes (e.g., status, sensor information, etc.) to a requestingentity.

Node Communication & Association Examples

To better illustrate how exemplary management and communicationprinciples may be implemented within an exemplary wireless node network,FIGS. 8-12 provide several examples of how exemplary components of thewireless node network may generally communicate (advertising &scanning), associate, and exchange information during different types ofoperations in various embodiments. FIGS. 22A-C also provide a moredetailed application of such exemplary association and communicationactivities when an exemplary ID node moves along a transit path (e.g.,through a corridor) and is tracked and managed by different master nodesand a server in an embodiment.

Node Advertising Cycle Example

As generally explained above, a node may have several different types ofadvertising states in which the node may be connectable with other nodesand may communicate with other nodes. And as a node moves within awireless node network, the node's state of advertising and connectionmay change as the node disassociates with a previously connected node,associates with a new node, or finds itself not associated with othernodes. In some situations, a node may be fine and in normal operationnot be connected or associated with another node. However, in othersituations, a node may raise an issue with potentially being lost if ithas not connected with any other node in a very long period of time. Assuch, a node may go through different types of advertising states inthese different operational situations.

Generally, a node may be in a state where it is not connectable withother nodes for a certain period of time (also referred to as anon-connectable interval). But later, in another state, the node maywant to be connected and advertises as such for a defined connectableperiod (also referred to as a connectable interval). As the nodeadvertises to be connected, the node may expect to be connected at somepoint. In other words, there may be a selectable time period withinwhich a node expects to be connected to another node. However, if thenode is not connected to another node within that period of time(referred to as an Alert Interval), the node may need to take specificor urgent action depending upon the circumstances. For example, if anode has not been connected to another node for 30 minutes (e.g., anexample alert interval), the node may change operation internally tolook “harder” for other nodes with which to connect. More specifically,the node may change its status flag from an Alert Level 0 (no issue,operating normal) to Alert Level 2 in order to request that anyavailable master node acknowledge receipt of the advertisement packetbroadcasted by the node seeking a connection.

FIG. 8 is a diagram illustrating exemplary advertising states (orinformation exchange and node connectability states) and factorsinvolved in transitions between the states by an exemplary ID node in awireless node network in accordance with an embodiment of the invention.Referring now to FIG. 8, three exemplary states for a node areillustrated as part of an exemplary advertising cycle for thenode—namely, an ID Node Non-Connectable Advertising state 805, an IDNode Discoverable Advertising state 815, and an ID Node GeneralAdvertising state 830. Transitions between these states will depend onfactors related to expirations of the types of intervals describedabove. In an embodiment, the duration of each of these intervals willdepend upon the system implementation and the contextual environmentwithin which the ID node is operating. Such time intervals may, forexample, be set by server 100 as part of data (e.g., profile data,association data, context data) provided to the node when updating thenode and managing operations of the node.

Referring to the example illustrated in FIG. 8, an exemplary ID node mayhave an alert interval set at, for example, 30 minutes, and be in IDNode Non-Connectable Advertising state 805 with a non-connectableinterval set at 5 minutes. In state 805, the ID node may broadcast oradvertise, but is not connectable and will not receive a SCAN_REQmessage (a type of request for more information sent to the advertisingnode from another node). Thus, the ID node in state 805 in this examplemay advertise in a non-connectable manner for at least 5 minutes butexpects to be connected within 30 minutes.

If the alert interval has not yet elapsed (factor 810) and thenon-connectable interval is still running (factor 825), the ID nodesimply stays in state 805. However, if the alert interval has notelapsed (factor 810) and the non-connectable interval elapses (factor825), the ID node will enter a mode where it wants to try to connect toanother node for a period of time (e.g., a 1 minute connectableinterval) and will move to the ID Node General Advertising state 830 inthe exemplary advertising cycle of FIG. 8. In state 830, as long as theconnectable interval is running, the ID node will stay in this statewhere it is connectable to another node and will receive SCAN_REQ typesof requests from other nodes in response to the advertising packets theID node is broadcasting. However, when the connectable interval (e.g.,the 1 min period) elapses or expires (factor 835), the ID node returnsback to the Non-connectable Advertising state 805 for either the nexttime the non-connectable interval elapses (and the ID node again triesto connect in state 830) or the alert interval finally elapses (and theID node finds itself in a situation where it has not connected toanother node despite its efforts to connect in state 830).

When the alert interval finally elapses (factor 810), the ID node movesto the ID Node Discoverable Advertising state 815. Here, the ID node isnot yet connectable but will receive a SCAN_REQ type of request fromother nodes in response to advertising packets the ID node isbroadcasting. In this state 815, the exemplary ID node may alter itsstatus flag to indicate and reflect that its alert interval has expiredand that the node is now no longer in normal operation. In other words,the ID node may change the status flag to a type of alert status beingbroadcasted to indicate the ID node urgently needs to connect withanother node. For example, the status flag of the advertising packetbroadcast by the ID node may be changed to one of the higher AlertLevels depending on whether the node needs to upload data (e.g., AlertLevel 3 status) or synchronize timer or other data with another node(e.g., Synchronize status). With this change in status flag, and the IDnode in state 815 broadcasting, the ID node awaits to receive a requestfrom another node that has received the broadcast and requested moreinformation via a SCAN_REQ message (factor 820) sent to the ID node fromthat other node. Once a SCAN_REQ message has been received by the IDnode (factor 820), the ID node that went into the alert mode because ithad not connected with another node within the alert interval canconnect with that other node, upload or share data as needed, and thenshift back to state 805 and restart the alert interval andnon-connectable intervals.

Master Node to ID Node Association Example

Advertising (broadcasting) and scanning (listening) are ways nodes maycommunicate during association operations. FIGS. 9-12 provide examplesof how network elements of a wireless node network (e.g., ID nodes,master nodes, and a server) may communicate and operate when connectingand associating as part of several exemplary wireless node networkoperations.

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment. Referring now to FIG. 9, exemplary master node M1910 a is illustrated within communication range of exemplary ID node A920 a. Master node M1 910 a also has a communication path back to server900. As shown, master node M1 910 a is in a scanning or listening mode(e.g., indicated by the “M1 _(scan)” label) while ID node A 920 a is inan advertising or broadcasting mode (e.g., indicated by the “A_(adv)”label). In this example, M1 master node 910 a has captured the addressof ID node A 920 a through A's advertising of at least one advertisingdata packet, and has reported it to the server 900. In this manner, thecapturing and reporting operations effectively create a “passive”association between the nodes and proximity-based custodial control.Such an association may be recorded in the server, such as server 900,as part of association data, such as association data 540.

In another embodiment, passive association between a master node and IDnode may be extended to an “active” association or connection. Forexample, with reference to the embodiment shown in FIG. 9, server 900may instruct master node M1 910 a to associate, connect, or otherwisepair with ID node A 920 a, and forwards the required securityinformation (e.g., PIN credentials, security certificates, keys) tomaster node M1 910 a. Depending on the advertising state of ID node A920 a, ID node A 910 a may only be visible (discoverable) but notconnectable. In such a situation, the master node M1 910 a must waituntil ID node A 920 a is in a connectable state (e.g., the ID NodeGeneral Advertising state) and can be paired. As discussed above withreference to FIG. 8, each ID node has a certain time window during eachtime period where it can be paired or connected.

In this example, when the ID node A 920 a is successfully paired withmaster node M1 910 a, ID node A 920 a may no longer advertise itsaddress. By default, only an unassociated device will advertise itsaddress. A paired or associated node will only advertise its address ifinstructed to do so.

ID Node to ID Node Association Example

In various embodiments, an ID node may associate with or connect toother ID nodes. FIG. 10 is a diagram illustrating exemplary componentsof a wireless node network during an exemplary ID-to-ID node associationin accordance with an embodiment of the invention. Referring now to FIG.10, exemplary master node M1 910 a, ID node A 920 a, and server 900 aresimilarly disposed as shown in FIG. 9, but with the addition of ID nodeB 920 b, which is within communication range of ID node A 920 a. In thisexample, ID node A 920 a is running in query (scan) mode (e.g.,A_(scan)) listening for ID node B 920 b. When ID node A 910 a detects IDnode B 920 b advertising (e.g., B_(adv)) with one or more advertisingdata packets as part of an advertised message from ID node B 920 b, IDnode A 920 a identifies a status flag from the message indicating IDnode B 920 b has, for example, data (e.g., sensor data 350) for upload.As a result, ID node A 920 a logs the scan result (e.g., as a type ofassociation data 340) and, when next connected to master node M1 910 a,ID node A 920 a uploads the captured scan log information to the server900. In this manner, the ID node scanning, capturing, and reportingoperations effectively create a “passive” association between thedifferent ID nodes. Such a passive association may be recorded in theserver 900 as part of association data 540.

In another embodiment, passive association between two ID nodes may beextended to an “active” association or connection. For example, withreference to the embodiment shown in FIG. 10, based upon the capturedstatus flag and uploaded information about ID node B 920 b under thatmode, the server 900 may issue a request to ID node A 920 a throughmaster node M1 910 a to actively connect or pair with ID node B 920 bfor the purpose of downloading information from ID node B 920 b. In oneexample, security credentials that authorize the active connectionbetween ID node A 920 a and ID node B 920 b are downloaded to ID node A920 a from master node M1 910 a, which received them from server 900. Inanother example, the requisite security credentials may have beenpre-staged at ID node A 920 a. And rather than rely upon an ID node toID node connection, master node M1 may have connected directly with IDnode B 920 b if M1 was within communication range of ID node B 920 b.

Information Query ID Node to Master Node Example

An exemplary ID Node may also issue queries to other nodes, both masternodes and ID nodes. FIG. 11 is a diagram illustrating exemplarycomponents of a wireless node network during an exemplary ID-to-masternode query in accordance with an embodiment of the invention. Referringnow to FIG. 11, a similar group of nodes as shown in FIG. 9 appears,except that exemplary master node M1 910 a is in an advertising orbroadcasting mode (e.g., M1 _(adv)) while ID node A 920 a is in ascanning mode (e.g., A_(scan)). In this configuration, ID node A 920 amay query master node M1 910 a for information. In one embodiment, thequery may be initiated through the ID node setting its status flag. Therequested information may be information to be shared, such as a currenttime, location, or environmental information held by the master node M1910 a.

In a passive association example, ID node A 920 a in A_(scan) mode mayhave captured the address of master node M1 910 a. However, since an IDnode cannot directly connect to the server 900 to request pairingsecurity credentials (e.g., security pin information that authorizes anactive connection between ID node A 920 a and master node M1 910 a), apassive association and corresponding pairing will have been initiatedfrom the master node. In another example, it may be possible for ID nodeA 920 a to have the pairing credentials stored as security data 335 froma previous connection. This would allow ID node A 920 a then to initiatethe active association with master node M1 910 a after a passiveassociation.

Alert Level Advertising Example

As previously noted, a node may enter an alert stage or level in one ormore embodiments. For example, if a node has not received anacknowledgement from a master node for an advertising packet within aset period (e.g., an Alert Interval as described in some embodiments),the node will enter a particular alert stage for more specializedadvertising so that it may be “found” or pass along information. FIG. 12is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary alert advertising mode in accordance with anembodiment of the invention. Referring now to FIG. 12, a similar groupof nodes as shown in FIG. 9 appears, with the addition of another masternode (master node M2 910 b) and another ID node (ID node B 920 b).Exemplary ID node A 920 a is in an advertising or broadcasting mode(e.g., A_(adv)) while nodes M1, M2, and B are each in scanning mode(e.g., M1 _(scan), M2 _(scan), and B_(scan)). In this example andconfiguration as shown in FIG. 12, the status flag in an advertisingmessage from ID node A 920 a has been set to a particular alert level(e.g., Alert Level 2) in the header of the message, requesting anynearby master node to acknowledge it. In one example, this mode may beentered if ID node A 920 a has not connected with another node for a setperiod or time. In another example, ID node A 920 a may enter thisspecialized advertising mode upon received instructions (e.g., fromserver 900 or another nearby node) or a triggered condition (other thantime), such as when a sensor input (such as light) is detected orotherwise registered and the node issues continuous updates of itsaddress as a security feature. The ID node A 920 a set at this alertlevel and in this specialized advertising mode is thus set in an activepairing mode, waiting for pairing credentials.

From a passive association perspective, any node in scanning mode canpassively associate with such an advertising node (e.g., ID node A 920 ain this alert mode). Thus, in an embodiment, the Alert Level 2 statusflag in the advertising header broadcast by ID node A 920 a indicatesthat urgent and active intervention is requested, rather than merelypassively associate without an active connection.

From an active association perspective, any node that uploads thespecial advertising header of ID node A 920 a may be forwarded thesecurity credentials from the server 900. This would allow for the nodereceiving such credentials to actively associate or pair with ID node A920 a.

While FIG. 8 provides examples of how a node may advertise, and FIGS.9-12 provide examples of how different exemplary devices (e.g., IDnodes, master nodes, and a server) may advertise and associate indifferent ways, FIGS. 22A-C provide a progressive set of illustrationsthat expand upon how associating and disassociating may be appliedwithin an exemplary wireless node network. More specifically, FIGS.22A-C show how associations and disassociations may occur when anexemplary ID node is tracked and managed by a server and differentmaster nodes as the ID node moves through an exemplary transit path inaccordance with an exemplary embodiment of the invention.

Referring now to FIG. 22A, a structure 2200 is shown having an entry andexit point. In one example, the structure 2200 may be a corridor oranother part of a building or facility. In another example, structure2200 may be a conveyor system that transports an item and its ID nodefrom the entry point to the exit point. Master node M1 2210 a is locatednear the entry point of structure 2200 while master node M2 2210 b islocated near the exit point. Those skilled in the art will appreciatethat other master nodes may be disposed at additional points instructure 2200, but are not shown for sake of convenience and tosimplify the association hand-off explanation that follows. Server 100is operatively connected to each of master node M1 2210 a and masternode M2 2210 b via network 105.

In one embodiment, server 100 has access to context data 560 related tothe structure 2200, such as layout data 585 on dimensions and materialsmaking up structure 2200. Context data 560 may include historic data 575on how an ID node has operated and successfully been tracked as ittraverses structure 2200 from the entry point to the exist point. Forexample, server 100 may have context data indicating structure 2200 is aconveyor that can transport an item and its ID node from the entry pointto the exit point over a distance of 800 feet. The context data mayfurther indicate typical items are moved at a certain speed on theconveyor of structure 2200 and a nominal time from the entry point tothe exit point may be about 5 minutes. Thus, the server 100 has accessto context data about the environment within with an ID node isoperating and may leverage this to better and more accurately manage theID node.

In FIG. 22A, ID node A 2220 a is shown entering the structure 2200 atthe entry point. Here, ID node A 2220 a may be advertising in hopes ofconnecting with a master node as it enters structure 2200 with, forexample, a non-connectable interval of 10 seconds with a connectableinterval of 5 seconds. In this example, the server 100 knows that IDnode A 2220 a is located near the entry point and anticipates that IDnode A 2220 a should be coming near to master node M1 2210 a at theentry point. Thus, server 100 may set the connectable andnon-connectable intervals accordingly so as to provide a sufficientopportunity for ID node A 2220 a to connect to the next master nodealong the predicted path of the ID node and in accordance with the speedof travel.

Additionally, server 100 may set the alert interval to 1 minute in thiscontext. Here, if ID node A 2220 a is not connected to another nodewithin 1 minute, ID node A 2220 a may broadcast or advertise with amessage having a changed status flag that indicates an alert status sothat ID node A 2220 a can connect to a broader range of other nodes thatsee it is urgent for ID node A 2220 a to connect and, essentially, befound. Depending on the context (e.g., the type of conveyor, the speedof the conveyor, the density of nodes near the entry point, etc.), thoseskilled in the art will appreciate that the server 100 can adjust theadvertising cycle intervals to better accommodate the ID node's currentenvironment.

When master node M1 2210 a is scanning (listening), it may initiallydetect an advertising packet from ID node A 2220 a during node A'snon-connectable interval. But when ID node A 2220 a changes advertisingstates and broadcasts as a connectable node in the general advertisingstate (i.e., during the connectable interval), master node M1 2210 a mayrespond with a SCAN_REQ that acknowledge receipt of the broadcastedmessage and asks for further information from ID node A 2220 a. Masternode M1 2210 a receives the requested information from ID node A 2220 a,and then communicates with the server 100 to notify the server of itspassive association with ID node A 2220 a. Server 100 determines ifactive association is desired, and may authorize the active associationbetween master node M1 2210 a and ID node A 2220 a by sending securitycredentials to master node M1 2210 a, which allow the nodes to securelyconnect and share information. And master node M1 2210 a may determinethe location of ID node A 2220 a (or server 100 may do so by directingmaster node M1 and/or ID node A), and provide the location of ID node A2220 a to server 100. Thus, server 100 is able to manage and track thelocation of ID node A 2220 a as it enters structure 2220 via at leastassociation.

In FIG. 22B, ID node A 2220 a has traversed down part of the transitpath through structure 2200 while remaining associated with master nodeM1 2210 a. However, at some point master node M1 2210 a and ID node A2220 a are disassociated at the direction of server 100 (or when theycan no longer communicate). In one example where ID node A 2220 a is onthe conveyor within structure 2200, server 100 may instruct ID node A2220 a to go to a low power mode for a particular period of time inorder to, for example, conserve ID node power. In another example, thelow power mode may also provide better location accuracy. As the server100 has access to the context data, the server 100 may know that ID nodeA 2220 a was associated with master node M1 2210 a near the entry pointat a given time, and determine that ID node A 2220 a will not be nearthe exit point until the end of the particular period of time. With theID node A 2220 a programmed this way, once the particular periodelapses, the ID node A 2220 a should be near the exit point and mayagain be placed into a normal operation mode so that it can seek toconnect with master node M2 2210 b.

Similar to the association process discussed with respect to ID node Aand master node M1, ID node A 2220 a and master node M2 2210 b may beassociated as ID node A 2220 a approaches master node M2 2210 b near theexit point. Once connected, the node locations and association data areupdated on the server 100. And as ID node A 2220 a continues to movethrough structure 2200, ID node A 2200 a may arrive at the exit point asshown in FIG. 22C, where the node locations and association data areupdated once again on the server 100.

Those skilled in the art will appreciate how such principles may beapplied to further movements of an ID node as it is handed off (e.g.,via active/passive associations and disassociations) between othermaster nodes and keeping track of these associations and node locationson the server 100. Additionally, as server 100 tracks and monitorsassociations, disassociations, and contextual environmental operations,server 100 essentially learns how to better use context informationbetter track nodes, manage power used by ID nodes, and enhance accuracyfor locations.

Those skilled in the art will also appreciate the general tradeoff witha level of RF power level and accuracy of location. If a node's RF powerlevel is set high, it may advertise and connect with other nodes alonger distance away. But at such a high power level setting, theability for the system to discriminate between and locate differentnodes may be a challenge.

Association Management within a Wireless Node Network

As explained above in general, management of nodes may rely uponassociations created and tracked between nodes and as indicated byassociation data generated on one or more of the nodes to reflect suchlogical associations. In some embodiments, the association relied uponmay be an active association where the server expressly authorizes anactive connection between nodes. In other embodiments, the associationrelied upon may be a passive association where the master node orcommand node (a type of managing node) is associated with the othernode, but not actively connected to the other node. By virtue of thepassive association, the server may be able to keep track of and managethe other node without requiring an active association. Thus, thoseskilled in the art will appreciate that in still other embodiments,associations relied upon for managing a wireless node network mayinclude both active and passive associations and may be generallyauthenticated or, more specially, authorize a secure connection that hasa degree of protection for the connection and communications using thatconnection.

Context Management within a Wireless Node Network

As explained above in general, management of nodes may rely upon thecontextual environment of the nodes. As shown in FIG. 5, server 100 hasaccess to a wide variety of different context data 560. Context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention. As such, the useof such context data provides a data foundation in an embodiment so thatthe server may better and more efficiently implement management tasksrelated to nodes in the network, and adjust such tasks to account forrelevant context data as nodes move within the network (e.g., as an IDnode moves with an item being shipped along an anticipated or predictedtransit path from an origin to a destination). For example, the servertake advantage of its ability to rely upon relevant context data toadvantageously alter how it instructs a node operate, how it associatesa node with the another node, how it can better locate a node, and howit can more efficiently track and respond to requests to report thelocation of the node.

Node Location Determination Methodologies

As part of managing and operating a wireless node network in accordancewith one or more embodiments of the invention, determining a node'slocation may be performed. As explained above, an exemplary ID node maybe directly or indirectly dependent on a master node to determine itslocation. In the embodiments discussed and described herein, a locationof a node may generally encompass a current or past location. Forexample, an embodiment that determines a node's location may be acurrent location if the node is not moving, but may necessarilydetermine the location as a past location should the node be in a stateof motion.

Likewise, the term location alone may include a position with varyingdegrees of precision. For example, a location may encompass an actualposition with defined coordinates in three-dimensional space, but use ofthe term location may also include merely a relative position. Thus, theterm location is intended to have a general meaning unless otherwiseexpressly limited to a more specific type of location.

Determining node location may done by a master node alone, the serveralone, or the master node working together with the server. And on suchdevices, embodiments may use one or more methodologies to determine anode's location and further refine the location. Such examplemethodologies may include, but are not limited to, determining nodelocation may relate to controlling an RF characteristic of a node (e.g.,an RF output signal level and/or RF receiver sensitivity level),determining relative proximity, considering association information,considering location adjustments for context information and an RFenvironment, chaining triangulation, as well as hierarchical andadaptive methods that combine various location methodologies. A moredetailed description of these exemplary node location determinationtechniques is provided below.

Location Through Proximity

In one embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes. If neithernode's actual location is known, one embodiment may infer a locationrelationship of the two nodes through proximity.

Proximity when Varying Power Characteristics

For example, an exemplary method of determining a node's location in awireless node network of nodes may involve varying a node's powercharacteristic, such as the output power of one of the nodes. Generallyand as explained with reference to FIG. 13, the power characteristic maybe varied to identify closer ones of the nodes to the node broadcasting.The node broadcasting may transmit one or a series of signals whileother nodes may report receiving one or more of the signals. Those othernodes that receive at least one signal broadcast from the transmittingnode may be deemed part of a close group of nodes. And as the powercharacteristic is varied (increased or decreased or both), a closestgroup of nodes (or single node) may be identified as the smallest groupof nodes of those that receive at least one signal from the broadcastingnode. Accordingly, while not absolute, a type of location for thebroadcasting node may be determined based on the closest one or group ofnodes. This may be repeated for neighboring nodes to yield a set ofclosest node information for each of the nodes. In more detail, anexemplary set of closest node information for each of the nodes mayinclude which nodes are closest (via the lowest power characteristic)and more robustly supplement this information with which other nodes areincrementally further away (via increasingly larger powercharacteristics). Thus, the set of closest node information provides thebasis for a determination of how close the nodes in the network are toeach other, which provides a type of location determination for eachnode.

Additionally, context data may be referenced in certain embodiments tofurther enhance determining how close the nodes are to each other. Forexample, combining the set of closest node information with contextdata, such as scan information that registers when an item changescustodial control in a delivery system, may further refine how todetermine the location of the nodes. Scan and other context informationwill help determine if one or more of the nodes, for example, are knownto be in the same container, vehicle or moving on a belt together. Thus,this type of context data may be integrated into a further step ofrefining how close the nodes are to each other based upon the contextdata.

In general, a location of a node based upon proximity may be determinedwhen a power characteristic of nodes is changed or varied in a wirelessnode network. An exemplary method for location determination by varyinga power characteristic of nodes in a wireless node network in accordancewith an embodiment of the invention begins by instructing a first of thenodes to vary the power characteristic for one or more signals broadcastby the first node. In a more detailed embodiment, such an instructionmay cause the first node, for example, to incrementally decrease orincrementally increase the power characteristic (such as an output powerlevel) between values.

This method continues by identifying a first group of other nodes in thewireless node network that are near the first node based upon those ofthe other nodes that received at least one of the signals broadcast bythe first node as the first node varies the power characteristic. In afurther embodiment, this identifying step may incrementally identifyingwhich of the first group of other nodes are receiving at least one ofthe broadcast signals as the first node incrementally varies the outputpower level of the signals broadcast. The incrementally identified nodesmay be deemed a set of increasingly close nodes to the first node.

The method continues by identifying a closest one or more of the othernodes as a smallest group of the other nodes that received at least oneof the one or more signals broadcast by the first node as the first nodevaries the power characteristic.

The method concludes by determining a location of the first node basedupon the closest one or more of the other nodes. Thus, as the powercharacteristic is varied, the group of nodes that have received at leastone of the signals broadcast by the first node may change and thesmallest such group being a closest group of nodes (even if just onenode) to the first node. In a more detailed embodiment, this determiningstep may comprise determining the location of the first node based uponthe closest one or more of the other nodes and the set of increasinglyclose nodes to the first node as the set of increasingly close nodesprovides more detailed proximity information for a refined locationdetermination.

For example, referring to FIG. 14, the set of increasingly close nodesto the ID node F 920 f may include node M3 as being farthest away and M1being closer than M3. When the power characteristic of ID node Fincrementally decreases, and its output power level changes from P1 toP2, M3 can no longer receive the signal, but M1 and M2 still do. And asthe power characteristic of ID node F continues to incrementallydecrease, and its output power level is changed from P2 to P3, M1 can nolonger receive the signal, but only M2 does as the last of the nodesclosest to ID node F. Thus, in this example, determining the location ofID node F may be based upon the fact that M2 is the closest node and theset of increasingly close nodes include M1 and M3 with M1 being closerthan M3.

In another embodiment, one or more further refinements to the firstnodes location may be performed. In one example, the steps of the abovedescribed locating by proximity technique may be repeated where a secondof the nodes is instructed to vary the power characteristic for one ormore signals broadcast by the second node, and then the method mayfurther refine the location of the first node based upon a location ofthe second node. In a more detailed example, the steps may be repeatedwhere a second of the nodes is instructed to vary the powercharacteristic for one or more signals broadcast by the second node, andthen this method may further the location of the first node based upon alocation of the second node and a set of increasingly close nodes to thesecond node. With this increasingly cross-related information on whatnodes are closer to other nodes and to what degree, which may be furtherrepeated for additional nodes, embodiments may further refine thelocation of the first node within the network.

This method may further include determining context data related to thefirst node, and refining the location of the first node based upon thecontext data. In an embodiment where the power characteristic is outputpower level, the incremental changes in the output power level of thebroadcast signal may be set according to the context data.

This method may also determine the context data to be related to theclosest node to the first node, and refine the location of the firstnode based upon the context data. In still another example, this methodmay determine the context data to be related to the incrementallyidentified nodes in the set of increasingly close nodes to the firstnode, and refining the location of the first node based upon the contextdata. For example, the closest node and the set of increasingly closenodes may have scan data that indicate they are within the samecontainer. This exemplary context data may be used to further refine thelocation of the node being located, which may help efficiently determinethat node is near the container. As such, those skilled in the willappreciate that context data for the node being located as well as nodesidentified to be close to that node may provide relevant input toadvantageously help further refine the location of the node.

Those skilled in the art will appreciate that this proximity locatingmethod as disclosed and explained above in various embodiments may beimplemented on a server apparatus, such as server 100 illustrated inFIG. 5, running one or more parts of server control and management code525 (e.g., the location manager). Such code may be stored on anon-transitory computer-readable medium such as memory storage 515 onserver 100. Thus, when executing code 525, the server's processing unit500 may be operative to perform operations or steps from the exemplarymethods disclosed above, including this method and variations of thatmethod.

An embodiment of such a server apparatus may include a server (such asserver 100) operative to communicate with a plurality of nodes in thewireless node network. As explained with respect to FIG. 5, the servergenerally includes a server processing unit, a server volatile memory, aserver memory storage, and at least one communication interface. In thisembodiment, the volatile memory, memory storage, and communicationinterface are each coupled to the processing unit. The memory storagemaintains at least a program code section and location data related to alocation of one or more of the nodes. The communication interfaceprovides a communication path operatively coupling the server with thenodes.

The server processing unit, as mentioned above, is operative whenrunning the program code section, to perform the steps and operations asdescribed above relative to the above described method for locating byproximity via varying power and variations of that method describedabove.

Proximity when Observing Signal Patterns and Strengths Over a TimePeriod

In another embodiment, an improved method for determining a node'slocation through proximity may include analyzing the signal patterns andstrengths between an advertising node and a listening node. In oneembodiment, a threshold may be set for association based on an observedmessage count and/or recorded signal strength within a specific timeperiod may improve the ability to locate a node (e.g., an ID node) tothat of another node (e.g., a master node). In some embodiments, theobserved message count may be implemented as an averaged count over arepeated time periods. Further still, other embodiments may filteroutlying observations in the observation data set to help improve thequality of data relied upon for setting a threshold for association and,as a result, determine a node's location.

In a more detailed example, an improved method for determining a node'slocation through proximity may show captured advertising message countsas a component for a node's location and determining a node's directionof travel. In this example, two exemplary master nodes (e.g., masternode M1 910 a and M2 910 b) may capture advertising messages from one IDnode (e.g., ID node A 920 a). Master node M1 may observe and capture(e.g., record information related to the observation) 60 messages fromID node A within a 2 minute period, while master node M2 only observesand captures 7 advertising messages from ID node A within that sameperiod. Based upon the difference in how often messages are observedfrom ID node A by master node M1 compared to those observed by masternode M2, the system is able to determine that ID node A would moreproximate to master node M1, and it's known location.

In a further embodiment, comparing the average time stamp of thecaptured records may allow the system can make a more accuratedetermination of location. For example, if the average captured messagefound on master node M2 is increasingly growing larger (e.g., takinglonger for messages to go from ID node A to master node M2), thisindicates ID node A is moving away from master node M2. If the averagecaptured message found on master node M2 is growing increasingly largerwhile the average captured message found on master node M1 isincreasingly growing smaller, this indicates ID node A is moving awayfrom master node M2 and toward master node M1. Thus, over a number ofobserved time periods, the change in message timing (transmission toreception) may also be relied upon to enhance or refine a node'slocation.

In yet another embodiment, the observed signal strength may be acomponent in location determination and estimating direction of traveland may allow the system can make a more accurate determination oflocation. For example, two master nodes (M1 910 a and M2 920 b) may becapturing advertising messages from a node (ID node A 920 a). M1captures 60 messages from ID node A within 2 minutes, while M2 capturesonly 7 messages. The average signal strength observed for signals fromID node A by master node M1 is higher compared to the average signalstrength observed by master node M2. Based upon this observed signalstrength information, the system would determine that ID node A to be atM1, but a predicted path may indicate ID node A is heading towards M2.As the master nodes M1 and M2 continue to capture records, the system(e.g., management code 524 operating on server 900, which is incommunication with M1 and M2) processes the continued feed of capturerecords from M1 and M2. With this observed signal strength information,the server 900 would expect that the count and average signal strengthof messages from ID node A over the time period observed (2 minutes) toincrease for observations at M2 and to decrease for observations at M1when ID node A is physically moving closer to M2 and away from M1. Thus,the change in observed powers levels and in how often messages areobserved may indicate actual node movement in an embodiment.

Basing node proximity location and node directional determinations onobserved signal patterns and characteristic strengths over a period oftime has the advantage of reducing the likelihood of unwanted andspurious signal anomalies causing an ID node's location to beincorrectly determined. And the above exemplary methods for determiningmovement characteristics of a node (e.g., moving closer to one node,moving closer to one but away from another, etc.) as part of refiningthe node location may be applied in combination with the variousembodiments for determining node location described herein.

FIG. 17 is a flow diagram illustrating an exemplary method for proximitylocating a node in a wireless node network based upon observed signalpatterns and characteristic indications over a period of time inaccordance with an embodiment of the invention. Referring now to FIG.17, method 1700 begins at step 1705 by instructing a first and a secondother nodes to detect any message broadcast from the one node over aperiod of time. The period of time may be set based upon a variety offactors, such as context data. In more detail, the period of time may bedynamically changed based upon context data as the one node moves intodifferent contextual environments.

Method 1700 has the server receiving a first indication from the firstother node at step 1710 and receiving a second indication from thesecond other node at step 1715. Finally, the method 1700 determines alocation of the one node based upon a difference in the first indicationand the second indication at step 1720.

The first indication is related to a characteristic of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time. Likewise, the second indication is related tothe characteristic of messages broadcast from the one node that aredetected by the second other node during the period of time. Theseindications may include, for example, a count of messages received bythe respective other nodes, a transit time factor (e.g., an averagetransit time for a message to be detected after broadcast), and anaverage signal strength.

In one embodiment, the first indication may be a first count of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time, and the second indication may be a secondcount of messages broadcast from the one node that are detected by thesecond other node during the period of time. As such, determining thelocation of the one node may be the location that is closer to the firstother node than the second other node when the first count is greaterthan the second count. Additionally, the method 1700 may further includedetermining an actual node movement direction for the one node basedupon comparing the first count and the second count over a plurality oftime periods. For example, the method 1700 may repeat observations overseveral of these time periods and track the first count and second countover time to determine which is increasing, which is decreasing, anddetermine movement of the one node based upon these measurements overtime.

In another detailed embodiment, the first indication may be a first timefactor of messages broadcast from the one node that are detected by thefirst other node during the predetermined time period, and the secondindication may be a second time factor of messages broadcast from theone node that are detected by the second other node during the period oftime. And an actual node movement direction for the one node may bebased upon comparing the first time factor and the second time factor.In a more detailed embodiment, the first time factor may be an averagetransit time for a message detected at the first other node to go fromthe one node to the first other node, and the second time factor is anaverage transit time for a message detected at the second other node togo from the one node to the second other node. As such, determining thelocation of the one node may be that the location is closer to the firstother node than the second other node when the first time factor is lessthan the second time factor.

In yet another embodiment, the first indication may be a first averagesignal strength of messages broadcast from the one node that aredetected by the first other node during the period of time, and thesecond indication may be a second average signal strength of messagesbroadcast from the one node that are detected by the second other nodeduring the period of time. As such, determining the location of the onenode may be that the location is closer to the first other node than thesecond other node when the first average signal strength is greater thanthe second average signal strength.

The method 1700 may also include, in an embodiment, observing a degreeof change in the first average signal strength and a degree of change inthe second average signal strength over repeated time periods, anddetermining an actual node movement direction for the one node basedupon comparing the degree of change in the first average signal strengthand the degree of change in the second average signal strength.

In another embodiment, the method 1700 may also refine the determinedlocation of the one node. In this embodiment, the method 1700 mayfurther comprise refining the location of the one node based upon atleast one of a first updated location received from the first other nodeand a second updated location received from the second other node. Forexample, when first other node is a mobile master node and it is thecloser of the two nodes to the one node being located, the embodimentcan take advantage of the location signaling onboard the first othernode that provides the current location of the first other node. Thatcurrent location data may be transmitted by the first other node to theserver to update the server in its calculation of the location for theone node.

In still another embodiment, the method 1700 may layer context data withthe determined location to refine the location of the node. Context datarelated to the one node may be determined by the server, and so thelocation of the one node may be refined based upon that context data. Inanother example, context data related to the closer of the first othernode and the second other node when compared to the location of the onenode. For example, the server may be aware that a particular master nodeis closer to the one node compared to a second master node, and that theparticular master node is within a container. With this additionalcontext data related to the particular master node, the server mayrefine the location of the one node based upon the context data. Otherexemplary types of relevant context data may be relied upon whenrefining the location of the one node, such as context data of aparticular shielding associated with the environment near the particularmaster node (e.g., a particular type of ULD having known RF shieldingcharacteristics, etc.)

Additionally, the method 1700 may involve looking to see if the one nodeis behaving as expected. More specifically, a further embodiment of themethod 1700 may further compare the location of the one node to apredicted path of the one node to determine if the one node is locatedoutside the predicted path. This may allow the server to use learned,historic data when creating a predicted path, and keep track of the onenode relative to being within an acceptable range associated with thispredicted path. The method may also generate a notification if the onenode is outside the predicted path. In this manner, actionable tasks canthen be taken to locate the one node—e.g., changing filter mode optionsfor nodes in that general area, etc.

Those skilled in the art will appreciate that method 1700 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIG. 5, running one or moreparts of server control and management code 525 (e.g., the locationmanager). Such code may be stored on a non-transitory computer-readablemedium such as memory storage 515 on server 100. Thus, when executingcode 525, the server's processing unit 500 may be operative to performoperations or steps from the exemplary methods disclosed above,including method 1700 and variations of that method.

Association Driven Locating with Variable RF Characteristics

As noted above, a signal strength measurement between two or more nodesmay be used to determine relative distance between nodes. If one of thenodes has a known location (such as master node M1 910 a), a relativelocation of one or more nodes within a range of the known location nodeis generally a function of how accurate the system may determine adistance between the node with known location and associated nodes. Inother words, an embodiment may identify a relative location of an itemand its related node by relying upon association-driven variablelow-power RF output signals to determine a distance the node is from aknown location.

Location Determination Through Master Node Advertise

As generally mentioned above, determining node location may relate tocontrolling an RF characteristic of a node (e.g., an RF output signallevel and/or RF receiver sensitivity level) and, more specifically, mayinvolve aspects of controlling master node advertising. FIG. 13 is adiagram illustrating an exemplary location determination using masternode advertise in accordance with an embodiment of the invention. In theillustrated embodiment shown in FIG. 13, a master node, such as masternode M1 910 a, with a known location is broadcasting an advertisingmessage at varying RF output power levels. FIG. 13 illustrates theexemplary different RF output power levels as concentric ranges1305-1315 about master node M1 910 a. Thus, master node M1 910 a maybroadcast at a maximum power P1, related to range 1305, but may controlthe RF output power level and dynamically change the RF output powerlevel to P2 and broadcast at a smaller range 1310, or to P3 andbroadcast to an even smaller range 1315.

In the illustrated embodiment, receiving ID nodes A-E 920 a-920 e are inquery (scan) mode and can each use the received signal at differentlevels to determine how far away from the transmitting M1 they arelocated. Those skilled in the art will appreciate that while theillustrated embodiment shown in FIG. 13 has the receiving nodes all asID nodes, other embodiments may have receiving nodes be either master orID nodes or a mixture.

In the exemplary embodiment of FIG. 13, the location for nodes A-E maybe determined based upon the known location of master node M1 910 a.That location, plus a range measurement when each of respectivereceiving nodes A-E last receives a signal from node M1, and factoringin a confidence factor of the range measurement, provides a locationdetermination for the nodes according to variable RF signal power.Depending on a quality of the range measurement, the individualreceiving nodes may or may not have an individually calculated location.In yet another embodiment, if third party or context data, such as scaninformation, is available, a refined location may be determined usingsuch data as an additional confidence factor. As the communication rangeof M1 is limited from P1 to P3, the accuracy of location by associationgoes up.

In the illustrated example of FIG. 13, an exemplary method ofdetermining a node's location may be described that uses master nodeadvertising. First, when the master node M1's variable power short rangecommunication interface 480 is set to P1, its maximum output, masternode M1 910 a is seen by each of ID nodes A-E 920 a-920 e. Based uponanalytics or historic measurements, the open air performance (optimalrange) of the radio in M1's variable power short range communicationinterface 480 at P1 power level may have been previously been found tobe approximately 30 feet. Thus, without the need to examine RSSI levelsfrom the individual ID nodes A-E 920 a-920 e and without the need foractive calibration phases, the system may know that ID nodes A-E arewithin 30 feet of master node M1 910 a.

Next, when the master node M1's variable power short range communicationinterface 480 is set to P2, a medium output level in this example,master node M1 is seen by nodes A and B. From previous analytics orhistoric measurements, it was determined the open air performance(optimal range) of the master node M1's variable power short rangecommunication interface 480 running at P2 power level is approximately15 feet. Thus, without the need to examine RSSI levels from theindividual nodes, we know ID nodes A 920 a and B 920 b are within 15feet of master node M1. Furthermore, we know the ID nodes no longerreceiving the broadcasted RF signal from master node M1 910 a (e.g., IDnodes C 920 c, D 920 d, and E 920 e) are somewhere within 30 feet ofmaster node M1 910 a, but probably more than 15 feet away from M1.

And when the master node M1's variable power short range communicationinterface 480 is set to P3, its minimum output level in this example, itis seen by ID node B 920 b. From previous analytics or historicmeasurements, it was determined the open air performance (optimal range)of the master node M1's variable power short range communicationinterface 480 running at P3 power level is approximately 5 feet. Thus,without the need to examine RSSI levels from the individual ID nodes, weknow the location of ID node B 920 b is within 5 feet of the knownlocation of master node M1 910 a.

The ranging steps, as discussed in the example above, may then berepeated for any of the identified nodes in order to build a moreaccurate picture of the relative location of each node. The granularityof RF characteristic settings (e.g., the RF output signal power levelsetting) will provide more granularity of location differentiation whenperforming the ranging steps. In one embodiment, the ranging steps maybe performed over a set of gross RF characteristics settings (e.g., fewsettings over a wide range), and similar steps may then be performedover more select ranges for the RF characteristics settings.

FIG. 19 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 19, method 1900 begins at step 1905 where a first of the nodesbroadcasts one or more first messages at a first anticipated orpredicted range distance. In one embodiment, the first anticipated rangedistance is an optimal range for the first node. For example, the firstnode's radio in its communication interface may have a maximum settingto allow the node to broadcast at maximized range assuming a clearenvironment. Such a setting provides a known anticipated range distance.In the example of FIG. 13, master node M1 910 a may be broadcasting at amaximum power level P1 that reaches a first range distance from node M1.However, if node M1 is known to be within an adverse RF shieldingenvironment, the first anticipated range distance may be a distanceadjusted to account for the contextual environment of such shielding(e.g., a type of context data). Anticipated range distances may beadjusted depending upon one or more types of relevant context (e.g., oneor more types of context data related to how an RF output signal fromthe node may be impeded).

At step 1910, method 1900 identifies which of the nodes associated withthe first node received at least one of the first messages. In oneembodiment, the first node may be able to access and review associationdata in its onboard memory storage as part of identifying which are thenodes associated with it. In one example, the associations with thefirst node may be passive associations (e.g., not actively paired andsecurely connected) or active associations (e.g., actively paired andable to securely connect and share data), or a combination of both typesof associations.

Next, at step 1915, the first node broadcasts one or more secondmessages at a second anticipated range distance, which is incrementallysmaller than the first anticipated range distance. In the example ofFIG. 13, master node M1 910 a may be the first node and now isbroadcasting at a medium power level P2 that reaches a secondanticipated range distance from node M1. By incrementally changing theRF power level in this manner, master node M1 910 a now no longer canreach nodes C-E as shown in FIG. 13.

At step 1920, method 1900 concludes by determining a location of one ormore of the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages, wherethe location is between the first and second anticipated range distancesfrom the first node. Again, in the example of FIG. 13, master node M1910 a may determine the location of nodes C-E (given they did notreceive the message sent out the second anticipated range distance at RFpower level P2) to between the first anticipated range distance (whenmaster node M1 was broadcasting at power level P1) and the secondanticipated range distance (when master node M1 was broadcasting atpower level P2) from the known location of master node M1.

In one embodiment, the method 1900 may also have the first nodebroadcasting one or more third messages at a third anticipated rangedistance (incrementally smaller range than the second anticipated rangedistance), and determining a location of one or more of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages, where the location isapproximately near the second anticipated range distance from the firstnode. Again, in the example of FIG. 13, by incrementally changing thepower level down to P1 and broadcasting a third message at ananticipated range distance for that P1 level, the master node M1 candetermine the location of node A (as node A received the second messagebut did not receive the third message) to be approximately near theanticipated range distance for P2 from the location of master node M1.

Additional embodiments of method 1900 may also refine such determinedlocations by updating the location of the first node. In one embodiment,the first node may be a mobile node. As such, refining may involvedetermining a current mobile location of the first node, and refiningthe location of the one or more of the identified associated nodes thatdid not receive any of the second messages but received at least one ofthe first messages based upon the current mobile location of the firstnode. Thus, as the first node moves and updates its own location (e.g.,via GPS signals received by location circuitry 475 on a master node),the first node is able to leverage its own updated location andadvantageously refine the location of nodes associated with it.

And, in some embodiments, the refined location of associated nodes maybe transmitted to a server. This provides an update to the server, andaids in tracking and managing the location of nodes in the network.Again, referring back to the example of FIG. 13, master node M1 910 amay take advantage of such a method for locating associated nodes, suchas the locations of ID nodes A-E 920 a-920 e, and update server 100 withthis new location data related to the current location of node M1 andany of the nodes associated with node M1.

Those skilled in the art will appreciate that method 1900 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4, or master node M1 910 a in FIG. 13)running one or more parts of master control and management code 425(e.g., the location aware/capture module). Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 110 a. Thus, when executing code 425, the master node'sprocessing unit 400 may be operative to perform operations or steps fromthe exemplary methods disclosed above, including method 1900 andvariations of that method.

In another embodiment, a node apparatus is described in a wireless nodenetwork that uses location determination by association as describedwith reference to the steps related to method 1900. As mentioned above,such as node apparatus may be implemented with a master node having anode processing unit, a node volatile memory, a node memory storage, anda first and second communication interface. Each of the memories andcommunication interfaces are coupled to the node processing unit.Further, the node memory storage maintains at least a program codesection, association data, and location data and, at times, shippinginformation. The first communication interface provides a firstcommunication path operatively coupling the node with a plurality ofother nodes in the network, while the second communication interfaceprovides a second communication path operatively and separately couplingthe node with a server in the network.

In this embodiment, the node processing unit is operative to transmitone or more first messages via the first communication interface at afirst anticipated range distance, and identify which of the others nodesthat are associated with the first node received at least one of thefirst messages. In one embodiment, the node processing unit may beoperative to access the association data in the node memory storage whenidentifying which of the nodes associated (e.g., passive, active, orboth types of associations) with the first node received at least one ofthe first messages.

The first anticipated range distance may be an optimal transmissionrange for the first communication interface and, in a more detailedexample, may be adjusted based upon context data (e.g., RF shieldinginherent from the surrounding environment of the node). In yet anotherembodiment, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal transmit from thefirst communication interface may be impeded by an environment of thenode.

The node processing unit is also operative to transmit one or moresecond messages via the first communication interface at a secondanticipate range distance (incrementally smaller than the firstanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the secondmessages but received at least one of the first messages. That locationis between the first anticipate range distance from a known location ofthe node and the second anticipated range distance from the knownlocation of the node. In a further example, the node processing unit maybe operative to store the determined location in the node memory storageas part of the location data.

The node processing unit may also be operative to transmit one or morethird messages via the first communication interface at a thirdanticipated range distance (incrementally smaller range than the secondanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the thirdmessages but received at least one of the second messages, where thelocation is between the second anticipated range distance from the knownlocation of the node and the third anticipated range distance from theknown location of the node.

In another embodiment, the node may be mobile and the node processingunit may be further operative to refine the location of the one or moreof the identified associated nodes that did not receive the secondmessage but received the first message by updating a location of thefirst node. In more detail, the node processing unit may be operative todetermine a current mobile location of the first node (e.g., check withlocation circuitry onboard the node for valid GPS signals and a locationlock based on such signals), and refine the location of the one or moreof the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages basedupon the current mobile location of the first node. The node processingunit may also be operative to transmit the refined location to theserver over the second communication interface.

Location Determination Through ID Node Advertise

While FIG. 13 provides an example of location determination throughmaster node advertising, FIG. 14 focuses on location determinationthrough ID node advertising. In particular, FIG. 14 is a diagramillustrating an exemplary location determination using ID node advertisein accordance with an embodiment of the invention. In the illustratedembodiment shown in FIG. 14, exemplary ID node F 920 f is in anadvertising mode but is without a known location. As with FIG. 13, FIG.14 illustrates the exemplary different RF output power levels from IDnode F 920 f as concentric ranges 1405-1415 about ID node F 920 f. Thus,ID node F 920 f may broadcast at a maximum power P1, related to range1405, but may control the RF output power level and dynamically changethe RF output power level to P2 and broadcast at a smaller range 1410,or to P3 and broadcast to an even smaller range 1415. Master nodes M1-M3910 a-910 c are disposed in various known locations relatively near IDnode F 920 f, which has an unknown location. As such, ID node F 920 fmay take advantage of the ability to adjust an RF characteristic, suchas RF output signal power level, of its own short-range communicationinterface as part of how the system may determine location of ID node Fthrough ID node advertising.

In the illustrated embodiment, an RF output signal power level of IDnode F 920 f may be varied or dynamically adjusted via programmablesettings (such as profile settings or parameters) related to operationsof variable power short range communication interface 375. Additionally,while an actual communication range may vary with the surroundingenvironment, a maximum anticipated communication range of the ID node'stransmitter at each power level is known assuming an optimal operatingenvironment or no substantial RF shielding or interference. Thus, aparticular power level setting for a broadcasting node is inherentlyassociated with a corresponding anticipated range distance.

In an exemplary method of determining a nodes location using ID nodeadvertising, the RF output signal power level may be varied acrossmultiple power levels to improve location through master nodeassociation. In more detail, when the ID node F's variable power shortrange communication interface 375 is set to P1, its maximum output, IDnode F 920 f is seen by each of master nodes M1-3 910 a-910 c. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 at P1power level may have been previously been found to be approximately 30feet. Thus, without any examination of RSSI levels from the individualmaster nodes, the system knows ID Node F is within 30 feet of masternodes M1-M3.

Next, when the ID node F's variable power short range communicationinterface 375 is set to P2, a medium output level in this example, IDnode F 920 f is seen by master nodes M1 910 a and M2 910 b. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 atrunning at P2 power level is approximately 15 feet. Thus, without anyexamination of RSSI levels from the individual nodes, we know masternodes M1 910 a and M2 910 b are within 15 feet of ID node F 920 f inthis example. Furthermore, we know the master node no longer receivingthe broadcasted RF signal from ID node F 920 f (e.g., master node M3 910c) is somewhere within 30 feet of ID node F 920 f, but probably morethan 15 feet away from node F in this example.

And when ID node F's variable power short range communication interface375 is set to P3, its minimum output level in this example, ID node F920 f is seen by only master node M2 910 b. The anticipated open airperformance or range distance (optimal range, or range based uponanalytics or historic measurements) of the radio in ID node F's variablepower short range communication interface 375 at P3 power level isapproximately 5 feet. Thus, without any examination of RSSI levels fromthe master nodes, we know the location of ID node F 920 f is within 5feet of the known location of master node M2 910 b in this example.

The ranging steps with respect to the changed RF characteristics of anadvertising ID node, as discussed in the example above, may then berepeated for any of the identified nodes in order to building a morecomplete picture of the relative location of each node.

Furthermore, the timing between such ranging steps may vary dynamicallydepending upon whether the node is moving. Those skilled in the art willappreciate that when moving, a quicker flow through such ranging stepswill help to provide better accuracy given the movement of nodes. Thus,the time interval between instructing a node to broadcast one or moremessages at a particular power level and then instructing that node tobroadcast one or more messages at a different power level may be desiredto be shorter when the node is moving, which can be determined basedupon context data. For example, the context data may indicate the nodeis within a node package an on a moving conveyor system. As such, thenode is moving relative to fixed master nodes that may be positionedalong the conveyor system. Thus, server may have the first node performthe ranging steps where power is varied in relative quick successioncompared to a situation where the context data indicates the node is notmoving or is substantially stationary.

FIG. 20 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention.Referring to FIG. 20 and how it explains a particular way to locate anode using associations and master node one or more master nodeadvertising techniques, method 2000 begins at step 2005 by instructing afirst of the nodes to broadcast one or more first messages at a firstpower level, the first power level being related to a first anticipatedrange distance. In one example, the first anticipated range distance maybe an optimal range for the first of the nodes (e.g., a transmissionrange that assumes there are no obstructions and a clear signal pathbetween nodes). In another example, the first anticipated range distancemay be an optimal range for the first node adjusted based upon contextdata (e.g., data related to the surrounding RF environment of the firstnode).

At step 2010, the method 2000 identifies which of the nodes associatedwith the first node have known locations at step 2010. For example, thistype of identification may be accomplished by reviewing association datathat indicates which of the nodes are associated with the first node(e.g., via passive association, via active association, or via acombination of both), determining which of the nodes are associated withthe first node based upon the reviewed association data, and identifyingwhich of those associated nodes have known locations.

The method 2000 continues at step 2015 by determining which of theidentified associated nodes received at least one of the first messages.Next, the method 2000 instructs the first node at step 2020 to broadcastone or more second messages at a second power level, where the secondpower level is related to a second anticipated range distance and thesecond power level incrementally smaller than the first power level. Ina further example, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal from the first nodemay be impeded.

At step 2025, method 2000 determines which of the identified associatednodes received at least one of the second messages. Method 2000concludes at step 2030 where the method determines a location of thefirst node to be at or between the first anticipated range distance andthe second anticipated range distance from each of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages.

As mentioned above, determining the node's location may be improved whenaccounting for movement. As such, an embodiment of method 2000 mayinstruct the first node to broadcast the one or more second messageswithin a time interval after instructing the first node to broadcast theone or more first messages. The time interval may be predetermined insome implementations, but also may be a dynamically set parameter inother implementations based upon context data related to the first node.In more detail, the time interval may be reduced from a prior value whenthe context data related to the first node indicates the first node ismoving, but may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary.

In another embodiment, method 2000 may further include instructing thefirst node to broadcast one or more third messages at a third powerlevel. Such a third power level is related to a third anticipated rangedistance and incrementally smaller range than the second anticipatedrange distance. Thereafter, the method may determining the location ofthe first node to be at or between the second anticipated range distanceand the third anticipated range distance from each of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages.

In another embodiment, method 2000 may comprise refining the location ofthe first node with an updated location of one or more of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages. For example,if the first node is associated with a mobile master node, the locationof the first node may be refined with an updated location of the mobilemaster node (which may be closer to the first node than previouslydetermined).

In a further embodiment, the first node in the operation of method 2000may not be self-aware of its own location. In another embodiment, thefirst node in the operation of method 2000 may have been previouslyself-aware of the location of the first node but may no longer beself-aware of the location of the first node prior to broadcasting theone or more first messages. In more detail, the first node may no longerbe self-aware of the location of the first node prior to broadcastingthe first message because of a change in the environment surrounding thefirst node. Such a change in the environment may be, for example, whenthe first node has moved inside a structure (e.g., building, vehicle,aircraft, container, etc.) that blocks location signals from beingreceived by the first node.

Those skilled in the art will appreciate that method 2000 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule) to control operations of an ID node (such as ID node F in FIG.14) as part of location determination via ID node advertising. Such codemay be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a. Thus, when executing code 425,the master node's processing unit 400 may be operative to performoperations or steps from the exemplary methods disclosed above,including method 2000 and variations of that method.

From an apparatus perspective, an exemplary node apparatus in a wirelessnode network that uses location determination by association maycomprises a node processing unit, node memory coupled to and used by thenode processing unit (e.g., a node volatile memory and a node memorystorage). The node memory storage maintains at least a program codesection, association data, and location data. The node apparatus furtherincludes a first communication interface that provides a firstcommunication path coupled to the node processing unit and operativelycoupling the node with a plurality of other nodes in the network. Forexample, the master node 110 illustrated in FIG. 4 includes such typesof operational structure.

The node processing unit (e.g., processing unit 400 of master node 110a), when executing at least the program code section resident in thenode volatile memory, is operative to perform specific functions orsteps. In particular, the node processing unit is operative tocommunicate an instruction to a first of the other nodes (e.g., an IDnode or master node temporarily operating as an ID node) via the firstcommunication interface to cause the first other node to broadcast oneor more first messages at a first power level, where the first powerlevel is related to a first anticipated range distance.

The first anticipated range distance may be an optimal range for thefirst of the nodes and, in more detail, an optimal range for the firstof the nodes adjusted based upon context data. In even more detail, thefirst anticipated range distance and the second anticipated rangedistance may be adjusted based upon one or more types of context datarelated to how an RF output signal broadcast from the first node may beimpeded.

The node processing unit is also operative to identify which of thenodes associated with the first node have known locations. To do this,the node processing unit may access and review association data storedon the node memory storage (e.g., data indicating what nodes arepassively or actively associated with the first other node), maydetermine which of the remaining other nodes are associated with thefirst other node based upon the reviewed association data, and mayidentify which of the remaining other nodes determined to be associatedwith the first other node have known locations.

The node processing unit is also operative to determine which of theidentified associated nodes received at least one of the first messages,and to communicate another instruction via the first communicationinterface to the first node to cause the first node to broadcast one ormore second messages at a second power level, where the second powerlevel being is to a second anticipated range distance and incrementallysmaller than the first power level.

Finally, the node processing unit is operative to determine which of theidentified associated nodes received at least one of the secondmessages, and then determine a location of the first node to be at orbetween the first anticipated range distance and the second anticipatedrange distance from each of the identified associated nodes that did notreceive at least one of the second messages but received at least one ofthe first messages.

In a further embodiment, the node processing unit may be operative tocommunicate a third instruction via the first communication interface tothe first node to cause the first node to broadcast one or more thirdmessages at a third power level. The third power level is related to athird anticipated range distance and incrementally smaller range thanthe second anticipated range distance. Additionally, the node processingunit may then be operative to determine the location of the first nodeto be at or between the second anticipated range distance and the thirdanticipated range distance from each of the identified associated nodesthat did not receive any of the third messages but received at least oneof the second messages.

In still another embodiment, the node processing unit is able to accountfor movement of the first node with a time interval between instructionssent to the first node. In particular, the node processing unit may befurther operative to communicate another instruction via the firstcommunication interface to the first node to broadcast the secondmessages within a time interval after instructing the first node tobroadcast the first messages. In a more detailed example, the timeinterval may be dynamically set based upon context data related to thefirst node. In even more detail, the time interval may beprogrammatically reduced from a prior value when the context datarelated to the first node indicates the first node is moving (e.g., thefirst node is on a moving conveyor system) and/or the time value of theinterval may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary (e.g., the node is within a node package recently placed in astorage area).

The node processing unit, in a further embodiment, may be operative torefine the location of the first other node with an updated location ofone or more of the identified associated nodes that did not receive atleast one of the second messages but received at least one of the firstmessages, and cause a second communication interface (e.g., medium/longrange communication interface 485 coupled to processing unit 400) totransmit the refined location to the server.

From a server perspective, FIG. 21 is a flow diagram (similar to FIG.20) illustrating yet another exemplary method for location determinationusing one or more associations of nodes in a wireless node network inaccordance with an embodiment of the invention. Those skilled in the artwill appreciate that while a server may operate to implement the stepsas laid out in method 2000 and discussed above, FIG. 21 provides moredetails as to how a server processing unit (such as processing unit 500running server code 525) may implement such a method at that level ofthe network via method 2100. In this more detailed embodiment, theserver is communicating directly with a master node (e.g., a first node)to direct and control how the master node interacts with and causesoperations to be undertaken on the ID node (e.g., a second node). Thus,step 2105 is similar to step 2005 but more precisely calls forcommunicating with a first node via a communication interface to cause asecond node in the network to broadcast one or more first messages at afirst power level at the request of the first node, where the firstpower level is related to and corresponds with a first anticipated rangedistance. Likewise, step 2120 is similar to step 2020 but more preciselycalls for communicating with the first node via the communicationinterface to cause the second node to broadcast one or more secondmessages at a second power level at the request of the first node, thesecond power level being related to a second anticipated range distanceand incrementally smaller than the first power level. The other steps ofmethod 2100 are similar to those illustrated and explained aboverelative to method 2000, and that the similar principles will apply tomethod 2100.

Those skilled in the art will appreciate that method 2100 as disclosedand explained above in various embodiments may be implemented on aserver (e.g., server 100 in FIG. 5) running one or more parts of servercontrol and management code 525 to direct a master node to controloperations of an ID node (such as ID node F in FIG. 14) as part oflocation determination via ID node advertising. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 100. Thus, when executing code 525, the server's processingunit 500 may be operative to perform operations or steps from theexemplary methods disclosed above, including method 2100 and variationsof that method.

And similar to the node apparatus described above, one embodimentincludes an exemplary server apparatus in a wireless node network thatuses location determination by association. The exemplary serverapparatus generally comprises a server processing unit, server memorycoupled to and used by the server processing unit (e.g., a servervolatile memory and a server memory storage). The server memory storagemaintains at least a program code section, association data, andlocation data. The server apparatus further includes a communicationinterface coupled to the server processing unit and that provides accessto a communication path operatively coupling the server with at least afirst node in the network.

The exemplary server processing unit, when executing at least theprogram code section resident in the server volatile memory, isoperative to perform specific functions or steps. In particular, theserver processing unit is operative to communicate with the first nodevia the communication interface to cause a second node in the network tobroadcast one or more first messages at a first power level at therequest of the first node, where the first power level is related to afirst anticipated range distance; identify which of the remaining nodesin the network associated with the second node have known locations;determine which of the identified associated nodes received at least oneof the first messages; communicate with the first node via thecommunication interface to cause the second node to broadcast one ormore second messages at a second power level at the request of the firstnode, where the second power level is related to a second anticipatedrange distance and incrementally smaller than the first power level;determine which of the identified associated nodes received at least oneof the second messages; and determine a location of the second node tobe at or between the first anticipated range distance and the secondanticipated range distance from each of the identified associated nodesthat did not receive any of the second messages but received at leastone of the first messages. And in a further embodiment, the serverapparatus' processing unit may be further operative to store thedetermined location in the server memory storage as part of the locationdata.

In another embodiment, the server apparatus' processing unit may beoperative to communicate with the first node via the communicationinterface to cause the second node to broadcast the one or more secondmessages within a time interval after communicating with the first nodeto cause the second node to broadcast the one or more first messages. Aspreviously mentioned, this type of time interval may dynamically setbased upon context data related to the second node. Context data mayalso be used as set forth above with respect to the node apparatus butapplied here to the second node—such was where the first anticipatedrange distance is the optimal range for the second node adjusted basedupon context data.

Master Node Location Determination Through Advertise

In another embodiment, a master node may no longer know its location.For example, such a situation may occur when a master node determinesit's current location via GPS location circuitry 475, but the masternode finds itself without access to an adequate number of GPS signals(e.g., it cannot determine a location due to the lack of a sufficientnumber of GPS signals from diverse GPS satellites). Such a situation mayhappen when the master node moves indoors is proximate to a structurethat interferes with the location signals.

In an exemplary embodiment where a master node attempts to determine itsown location via advertising techniques, the master node may detect aloss of location confidence (e.g., upon a loss of detected GPS signals;upon detecting a separate signal to processing unit 400 indicating themaster node's location is unknown; when processing unit 400 sensesmovement (e.g., via accelerometers (not shown) or the like) but cannotconfirm that the location circuitry 475 is providing updated locationinformation for the node, etc.). In other words, the master node becomesaware that it no longer has a known location.

Next, the master node responds by beginning to broadcast one or moreadvertising messages in a similar way as ID node F 920 f is described asdoing with respect to FIG. 14. This is done so that the master nodehaving an unknown location can advantageously leverage off the knownlocations of nearby other nodes. As such, an embodiment may allow a typeof leveraged chaining effect whereby known locations of particular typesof nodes may be used to extend location information to other nodes thatdo not know their locations (e.g., ID nodes) or nodes that have detecteda loss of location confidence (e.g., master nodes). Thus, such anembodiment may be used to determine an indoor location of a master node(including equipment equipped with master node functionality) in caseswhere signals for the conventional onboard location circuitry 475 arenot available.

Referring back to the exemplary method 2000 and FIG. 20, method 2000 maybe such that the first node is not self-aware of the location of thefirst node. This may happen when the first node (e.g., an ID node) isactually a master node that was previously self-aware of its ownlocation (e.g., via received GPS signals) but is no longer self-aware ofits location (e.g., when the GPS signals can no longer be received),which has the master node changing operation to operate as an ID nodeprior to broadcasting the first message. In other words, the master nodemay no longer be self-aware of its location and begin operating as an IDnode for purposes of location determination prior to broadcasting thefirst message because of a change in the environment surrounding themaster node, such as when the master node has moved inside a structurethat blocks location signals from being received by the master node.Thus, an embodiment may advantageously allow a node to adaptively alteroperations when moving from a clear outdoor environment to an indoorenvironment. And a server may interact with such a master node whilethat master node is operating, for location purposes, as an ID node,temporarily.

Location with Improved RSSI Measurements

In another embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes by using oneor more improvements to conventional RSSI measurements. In conventionalRSSI measurements, such as with Bluetooth 4.0, those skilled in the artwill appreciate that adaptive frequency hopping as part of spreadspectrum techniques may cause undesirably cause the signal strength tofluctuate. In other words, the advantage of using frequency hopping andspread spectrum for security and avoidance of interference may have anegative impact on using such signals for stable proximity-basedlocation determinations. Thus, it may be desired to emphasize stabilityof a signal and limits to fluctuation for purposes of locationdetermination.

In one embodiment, a type of improvement for RSSI measurements mayinclude reducing the number of channels and/or a corresponding frequencyrange in use during advertising from nodes. For example, a node may haveprocessing unit 300/400 adaptively control variable power short rangecommunication interface 375/480 to reduce the number of channels and/orthe frequency range used during node advertising. Such a dynamic changemay be implemented, in some embodiments, by altering the content of aparticular type of profile data 330/430, such as an RF profile data thateffectively defines RF characteristics of a node (e.g., frequency, powerlevel, duty cycle, channel numbers, channel spacing, alternativefluctuation modes, etc.). In one further embodiment, a first fluctuationmode may be defined that provides a default or more standardcommunication protocol, such as the conventional frequency hopping,spread spectrum, and channel allocations for Bluetooth® communications.Other alternative modes (one or more) may be defined that alter one ormore RF characteristics to provide increasingly more stable and lessfluctuations of the RF output signal from a node. Thus, a node may bedynamically placed into one or more modes regarding such RFcharacteristics that increasingly emphasize stability of the node's RFoutput signal and limits fluctuation for purposes of enhanced locationdetermination using RSSI measurements.

In another embodiment, a type of improvement for RSSI measurements mayinclude ensuring visibility to and advantageously managing automaticgain control (AGC) circuitry (not shown) that may cause the RF outputsignal to vary for a node. For example, a node may include a type of AGCcircuitry as part of variable power short range communication interface375/480. This type of AGC circuitry may allow node processing unit300/400 or other logic circuitry that is part of variable power shortrange communication interface 375/480 to limit fluctuations undercertain conditions (e.g., when attempting to use RSSI locationdetermination techniques). In this example, different AGC circuitrysettings may be defined in exemplary RF profile data that effectivelydefines RF characteristics of a node (e.g., frequency, power level, dutycycle, channel numbers, channel spacing, alternative fluctuation modes,etc.). This is yet another example of how a node may be dynamicallyplaced into one or more modes regarding such RF characteristics(including AGC circuitry settings) that increasingly emphasize stabilityof the node's RF output signal and limits fluctuation for purposes ofenhanced location determination using RSSI measurements.

Location with Adjustments for Environmental Factors in RF Signal Quality

In general, those skilled in the art will appreciate that environmentalfactors may cause a communication signal, such as an RF signal, tofluctuate or be transmitted and received in a manner that undesirablyvaries depending upon a signal path environment. Passive physicalinterference factors (e.g., forms of electronic signal shielding) may besubstantially close and cause drops in signal strength across the outputranges of the nodes. Additionally, active radio interference factors mayvary across the RF output ranges of the nodes depending upon otheractive devices in the reception vicinity. Thus, the proximateenvironment of a node may have a multitude of adverse factors thatimpact communications and, as a result, the ability to locate the node.

In one embodiment, making location determinations may be enhanced by adata analytics type of approach that may adjust and account fordifferent RF environmental factors for a similar type of node in asimilar type of situation. For example, the quality of the RF outputsignal of a particular type of node and the corresponding physical rangeof that signal to a receiver of known sensitivity may be determined fora given environment. In this example, the system defines a maximum rangeof that signal based on a predetermined condition, such as open-airconnectivity. This may assume an environment with no signal degradationdue to interference or physical shielding. However, both interferenceand physical shielding may diminish the range of the RF output signal ofa node. In a dynamically adaptive and learning manner, the system maycollect information on how a particular type of node may operate in aparticular environment under certain settings (e.g., reported signalstrengths and corresponding settings for RF output signal power levels).This analysis of a similar environment may be repeated. In other words,through such data analytics of an anticipated environment to be faced bya similar node, signal loss information can be generated and applied asa type of context data (i.e., RF data) for a node in a similarenvironment to refine location determination. Thus, an exemplaryembodiment may refine location determinations with adaptive signal losscharacteristics based on a contextual appreciation of an anticipatedenvironment (e.g., physical shielding such as packaging, packagecontents, proximate package, proximate package contents, and physicalinfrastructure causing signal variance) without requiring a calibrationphase.

And advantageously combining those data points with 3^(rd) party datadescribing the physical environment, in which the node was located in atthat time, may refine location even further. Such information may beused as RF data (a type of context data) in future efforts to manage andlocate a similar type of node anticipated to be in a similarenvironment.

In more detail, in an embodiment that refines a location determinationbased upon context and data analytics to adjust for known RFimpediments, the maximum physical range of a node's RF output signalrelative to a receiver of known RF sensitivity is determined. In oneexample, this first range value may be referred to as a theoretical ornominal open-air range of a similar type transmitter-receiver node pairin a similar environment but with substantially no physical shielding orsignal interference negatively impacting the signal range. A secondrange value, which may be considered an actual RF range value, may bethe observed range of the signal in a similar environment but wherethere are contextual factors reducing the communication range, includingphysical shielding due to factors like packaging, package contents,proximate package, proximate package contents, physical infrastructure,interference from other radio sources, or shipper specific informationsuch as vehicle or facility layout information. Through access to priordata analysis of the differing range values and with knowledge of theoperational environment of the transmitting node was in (e.g., a similarenvironment to the proximate environment of the node), a refinedlocation may be determined using an approximation of an actual RF outputrange that intelligently adjusts what may be anticipated to be the RFenvironment of the node. In other words, by knowing the appropriatecontextual environment related to a node (such as signal degradationinformation on how a similar node operates in a similar environment), animproved location determination may be made to make intelligent yetefficient adjustments (such as communication distance adjustments) thatprovide a refined location of the node.

In one example, such as the example shown in FIG. 2, master node 110 bis outside of a container (such as a Uniform Load Device (ULD) container210 known to be used for transporting groups of items on aircraft) thathas an ID node inside the container. A first or theoretical range valuebetween master node 110 b and ID node 120 b may be determined to be 10feet at a specific RF output power level when the package (and relatedID node) may be known to be less than 10 feet away from the scanningnode (e.g., master node 110 b). A second range value at similardistances with similar types of nodes, but with incident RF signal lossas a result of communicating through the wall of the container 210, maybe between 4 and 5 feet. If context data, such as 3^(rd) partyinformation or scan data, indicates the transmitting node is within theULD container 210, the system would expect the transmission range to belimited according to the data analytics associated with this known RFimpediment (e.g., characteristics for transmitting through ULD container210), thus reducing the possible scanning nodes that may see thebroadcasting node within the ULD container, or require the transmittingnode to increase its RF output power to be heard.

FIG. 22 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention.Referring now to FIG. 22, method 2200 begins at step 2205 with a networkdevice (such as a master node or server) accessing a first type of thecontext data related to a proximate environment of the first node.

The first type of context data comprises signal degradation informationon how a second node would operate in a similar environment to theproximate environment of the first node when the second node is asimilar type as the first node. Thus, rather than calibrating with anactual measurement relative to the current proximate environment of thefirst node, the signal degradation information provides compensationinformation on what may be generally anticipated in a more generalproximate environment based on how a similar type of node may operate ina similar environment. As the similar environment of the similar node isgenerally an approximation for what is anticipated to be the proximateenvironment of the first node, this advantageously avoids the need foran actual calibration of the proximate environment. In one embodiment,the signal degradation information may be based upon a difference in howthe second node communicates when exposed to an adverse communicationenvironment (such as a similar environment to the proximate environmentof the first node) compared to how the second node would communicateswhen exposed to a nominal communication environment (such as anenvironment that is unencumbered by shielding and interference factors).Those skilled in the art will appreciate that a nominal communicationenvironment need not be perfectly clear of all influences that shield orinterfere with communications.

The types and aspects of signal degradation information may varydepending on a wide variety of factors. In one embodiment, the signaldegradation information may be related to at least one of shielding andinterference. Thus, signal degradation information may include bothpassive and active factors that impact the communication environment.

In another embodiment, the signal degradation environment may be basedupon a degraded operation of the second node when the similarenvironment is an adverse communication environment. In more detail, thesignal degradation information may be based upon a difference in how thesecond node communicates when exposed to the adverse communicationenvironment compared to how the second node communicates when exposed toa substantially normal communication environment, such as an open airenvironment.

In still another embodiment, signal degradation information may relateto at least shipment data for one or more items being shipped (e.g.,currently shipped or shipped in the past) and located in the proximateenvironment of the first node. For instance, a package near the firstnode may include metallic materials that may impede or block RF signalsand the signal degradation information may relate to such informationabout close packages being shipped near the first node. In anotherexample, the signal degradation information may relate to at leastlayout data for one or more physical structures in the proximateenvironment of the first node. In more detail, the layout data may befor one or more physical structures (e.g., walls, machinery, enclosures,and conveyances) in the proximate environment of the node near apredicted path for the first node. In yet another example, the signaldegradation information relates to at least historic data on one or moreanalyzed prior operations of the second node.

At step 2210, the network device, such as a master node or server, mayadjust an anticipated communication distance related to the first nodebased upon on the first type of the context data. In one example, theanticipated communication distance may be a theoretical broadcastdistance based upon parameters of the device's radio. Such ananticipated communication distance is known as it is an estimate of theradio's range. In one example, the adjusted communication distancecomprises an anticipated reduced range distance for a transmission fromthe first node. In another example, the adjusted communication distancecomprises an anticipated reduced receiver sensitivity distance for thefirst node.

In yet another example, adjusting the communication distance may beaccomplished by adaptively adjusting, by the network device, thecommunication distance based upon the signal degradation information anda second type of the context data. In other words, the communicationdistance may be adjusted based upon signal degradation informationconsidered along with other types of context data, such as how the firstnode is being moved (such as an anticipated movement of the first nodealong a predicted transit path for the first node) or a density of othernodes near the first node.

At step 2215, the network device determines the location of the firstnode based upon the adjusted communication distance. In a furtherembodiment, the method may also update the adjusted communicationdistance by the network device based upon movement of the first node,and may refine the location of the first node with an updated adjustedcommunication distance. This may happen with the first node is a mobilemaster node capable of self-determining its own location.

Those skilled in the art will appreciate that method 2200 as disclosedand explained above in various embodiments may be implemented on anetwork device (e.g., exemplary master node 110 a in FIG. 4 or server100 in FIG. 5) running one or more parts of their respective control andmanagement code to perform steps of method 2200 as described above. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a or memory storage 515 on server100. Thus, when executing such code, the respective network device'sprocessing unit may be operative to perform operations or steps from theexemplary methods disclosed above, including method 2200 and variationsof that method.

In more detail, an exemplary network device apparatus for determining alocation of a first node in a wireless node network based on contextdata, the exemplary network device may include a processing unit, avolatile memory coupled to the processing unit, and a memory storagecoupled to the processing unit. The exemplary network device furtherincludes a communication interface coupled to the processing unit andthat provides a communication path operatively coupling the networkdevice with the first node in the network.

The memory storage for the device maintains at least a program codesection and context data having at least signal degradation information.Such signal degradation information, as a type of context data, isinformation on how a second node would operate in a similar environmentto a proximate environment of the first node when the second node is asimilar type as the first node. Examples of signal degradationinformation may include those discussed above relative to step 2205 ofmethod 2200.

When executing at least the program code section when resident in thevolatile memory, the processing unit of the network device is operativeto perform the steps noted and described above with respect to method2200. In more detail, the processing unit is operative to at leastconnect with the memory storage to access the signal degradationinformation, adjust a communication distance (if needed) related to thefirst node based upon on the signal degradation information, determinethe location of the first node based upon the adjusted communicationdistance, and store the determined location of the first node aslocation data on the memory storage.

Adjusting the communication distance by the processing unit may beaccomplished as described above with regard to step 2210 of method 2200.And as mentioned above, the processing unit may be further operative toadaptively adjust the communication distance where other types ofcontext data are also considered, such as movement and anticipated nodemovement as detailed out above.

In a further embodiment, the network device may be a mobile master nodethat includes location circuitry (such as GPS circuitry 475 of exemplarymaster node 110 a shown in FIG. 4). In this embodiment, the processingof the network device may be further operative to determine a locationof the network device based upon an output signal from the locationcircuitry received by the processing unit, and determine the location ofthe first node based upon the adjusted communication distance and thelocation of the network device. As such, the first type of the contextdata related to the proximate environment of the first node is basedupon the determined location of the first node.

Those skilled in the art will also appreciate that in some operationalenvironments, the signal degradation information may not require anyadjustment to the communication distance in an embodiment. However, inother environments (e.g., adverse RF environments), the signaldegradation information may provide a basis for adjusting thecommunication distance in the embodiment, even if not performed everytime. Thus, an adjustment to the communication distance may not beneeded in all proximate environments of the first node but may beperformed, if needed, based on the proximate environment of the firstnode. It is the ability of an embodiment to adjust this communicationdistance when needed and if needed that advantageously allows forlocating the first node with more accuracy.

Location Through Triangulation

In some embodiments, various methods for determining a node's locationmay rely upon, at least in part, triangulation techniques. In otherwords, as the wireless node network collects data onreceiver-transmitter pairs, other methods for determining location ofthe individual nodes that utilize triangulation, at least in part, maybecome possible. FIG. 15 is a diagram illustrating an exemplary locationdetermination through triangulation within a wireless node network inaccordance with an embodiment of the invention. Referring now to theillustrated embodiment of FIG. 15, three exemplary master nodes M1-M3910 a-910 c are shown with each master node having a known location.Exemplary ID nodes A-E 920 a-920 e are also shown where they are atleast in communication range of one or more of exemplary master nodesMA-M3 910 a-910 c.

In this illustrated example, the master nodes M1-M3 may detect andcollect advertising messages from ID nodes A-E at varying and knownpower levels. The captured information is forwarded by the master nodesM1-M3 to the backend server 100, where location determinations may bemade. For example, factors like RSSI and visibility of each node at eachpower level may be used to determine, with a higher degree of accuracy,the location of nodes where sufficient information is available.

For an exemplary system to triangulate a node, three nodes with knownlocations must have seen the broadcasting node. In this example, twoadvertising ID nodes, A 920 a and B 920 b, were seen by the three nodeshaving known locations (master nodes M1-M3 910 a-910 c). Based upon thecaptured information, the locations of ID node A 920 a and ID node B 920b are calculated.

Chaining Triangulation

In another embodiment, a node with an inferred location may be used withtriangulation techniques to determine a location of another node in awireless node network. FIG. 16 is a diagram illustrating an exemplarylocation determination through chaining triangulation in accordance withan embodiment of the invention. The locations of ID nodes A 920 a and B920 c have been determined by triangulating across master nodes M1-M3,as illustrated in the exemplary embodiment shown in FIG. 15. However, asillustrated in FIG. 16, the location of ID node C 920 c may also bedetermined according to an embodiment.

For example, an exemplary method of determining a node's locationthrough chaining triangulation begins with determining the calculatedlocation of ID node B 920 b (as explained with reference to FIG. 15).Next, a node closer to ID node B 920 b may be used to get the missingthird signal point needed for triangulation. This may be accomplished byplacing ID node B 920 b in a query (scan) mode such that it listens fora message from ID node C 902 c. ID node C is instructed to advertise,thus providing a signal that may be captured by ID node B. Aftercapturing the signal profile of C, ID node B may communicate or sharethe captured information and forward it along to the backend server 100through either of the master nodes M1 or M2. The resulting locationdetermination of ID node C 920 c may have a higher level of positionerror due to it being partially based on a calculated reference (e.g.,the location of ID node B), but the leveraged location determination ofID node C 920 c may be sufficiently accurate (or be an actionablelocation) that useful information may be gleaned about ID node C 920 c.For example, a leveraged or chained location determination of ID node Cmay indicate, with the help of context data, that nodes M1, M2, and IDnode B are all close enough to ID node C that ID node C is determined tobe within the same command nodes M1, M2, and ID node B.

Location Through Proximity to Triangulation (LP2T)

In an embodiment where chaining triangulation may determine locationthrough proximity to triangulation (LP2T), a starting point may bedetermining the relative location of an ID node to a master node basedon the proximity method, as explained above. However, when the relativelocation of the ID node has been determined, a more accurate or refinedlocation of the ID node may be determined based upon the location of allmaster nodes that can capture the RF output signal broadcast from the IDnode, and then triangulating based on observed signal strength of the IDnode. In this example, the proximity-based location is used as an inputin the triangulation calculation to estimate likely signal deteriorationhistorically observed between a node at the proximity-determinedlocation and scanning master nodes. In a further embodiment, by takinginto account historic data on patterns of signal deterioration, a moreaccurate triangulation may be possible, leading to a more accuratelocation determination.

FIG. 23 is a flow diagram illustrating an exemplary method fordetermining a node location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention. Such an exemplary nodelocation need not be precise or exacting, but can be sufficientlyaccurate without absolutes.

Referring now to FIG. 23, method 2300 begins at step 2305 with theserver receiving a location of a first of the nodes from the first node.Next, at step 2310, the server receives a location of a second of thenodes from the second node. For example, with reference to the exampleshown in FIG. 16, master nodes M1 910 a and M2 910 b may transmit theirrespective location coordinates from their respective onboard locationcircuitry to the server so that the server has the current locations ofthese two master nodes.

At step 2315, the server infers a location of a third of the nodes. Forinstance, in the example illustrated in FIG. 16, the server may inferthe location of ID node B 920 b. In one embodiment, inferring maycomprise having the server determine a proximate-based location of thethird node relative to another of the nodes having a known location,such that the proximate-based location operates as the inferred locationof the third node.

In another embodiment, inferring the location of the third node maycomprise having the server determine a relative location of the thirdnode to the first node (as the node having a known location) or to thesecond node (as another node having a known location). Method 3300 mayalso, in another embodiment, include having the server adjust theinferred location of the third node to determine a refined location ofthe third node based upon third node context data related to theinferred location of the third node

At step 2320, method 2300 concludes with the server triangulating thelocation of the one node based upon determined distances to each of thefirst and second nodes, and a determined distance of the one node to theinferred location of the third nodes.

In a more detailed embodiment, method 2300 may triangulate the locationof the one node by accessing first node context data related to acontextual environment near the first node and second node context datarelated a contextual environment near the second node. Such contextualenvironments may include an environment of being on a conveyor system,or within a particular facility, or next to materials that may degradeor shield signals being received by the one node. Next, the moredetailed triangulating may have the server adjust the determineddistance of the one node to the location of the first node based uponthe first node context data to provide a refined distance of the onenode to the location of the of the first node. Then, the server maytriangulate the location of the one node based upon the adjusteddetermined distance of the one node to the location of the first node,the adjusted determined distance of the one node to the location ofsecond node, and a determined distance of the one node to the refinedlocation of the third node.

In a further embodiment, method 2300 may also have the servertransmitting an instruction so as to cause the server to transmit aninstruction to cause the one node to broadcast a plurality ofadvertising signals over a period of time. In such an embodiment, thedetermined distance of the one node to the location of the first nodemay be based upon captured signals from the one node by the first nodeover the period of time and reported to the server by the first node. Inanother embodiment, the determined distance of the one node to thelocation of the second node may be based upon captured signals from theone node by the second node and reported to the server by the secondnode.

In still another embodiment, the server may transmit an instruction tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. In another embodiment, the determined distanceof the one node to the location of the second node may be based uponcaptured signals from the one node by the second node and reported tothe server by the second node.

In yet another embodiment, method 2300 may also have the servertransmitting the location information out to a requesting entity (e.g.,another node, a user access device, etc.) upon receipt of a request fora location of the one node from that entity.

Those skilled in the art will appreciate that method 2300 as disclosedand explained above in various embodiments may be implemented on aserver (such as exemplary server 100 as illustrated in FIG. 5) runningone or more parts of a control and management code (such as an code 525)to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 515 in an exemplary server). Thus, when executing such code, aprocessing unit of the server (such as unit 500) may be operative toperform operations or steps from the exemplary methods disclosed above,including method 2300 and variations of that method.

A server apparatus is also described in an embodiment for determining alocation using chaining triangulation for one of a plurality of nodes ina wireless node network. The server apparatus generally comprises aserver processing unit, a server volatile memory, a server memorystorage, and a communication interface. The server volatile memory,server memory storage, and communication interface are each configuredin the apparatus as coupled to the server processing unit. The servermemory storage maintains at least a program code section and locationdata related to nodes in the network. In some embodiments, the servermemory storage may also maintain context data, such as first nodecontext data and second node context data. The communication interfaceprovides a communication path operatively coupling the server with nodesin the network, such as a first and second node.

The server processing unit, when executing at least the program codesection resident in the server volatile memory, is operative to performvarious functions, such as the functions described in the steps aboverelated to method 2300. In particular, the server processing unit isoperative to receive a request over the communication interface for thelocation of the one node. Based on the request, the server processingunit is then operative to receive the respective locations of the firstand second nodes, and store the locations as part of the location datakept on the server memory storage. The server processing unit is furtheroperative to infer a location of a third of the nodes, and store theinferred location of the third node as part of the location data kept onthe server memory storage. The server processing unit then is operativeto triangulate the location of the one node based upon a determineddistance of the one node to the location of the first node, a determineddistance of the one node to the location of second node, and adetermined distance of the one node to the inferred location of thethird node. And finally, the server processing unit is operative totransmit the location information to the requesting entity over thecommunication interface in response to the request.

In one embodiment, the server processing unit may be further operativeto infer the location of the third of the nodes by being operative todetermine a proximate-based location of the third node relative toanother of the nodes having a known location, where the proximate-basedlocation operates as the inferred location of the third node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals overa period of time. In this embodiment, the determined distance of the onenode to the location of the first node may be based upon capturedsignals from the one node by the first node over the period of time andreported to the server by the first node. Alternatively, the determineddistance of the one node to the location of the second node may be basedupon captured signals from the one node by the second node and reportedto the server by the second node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. Alternatively, the determined distance of theone node to the location of the second node may be based upon capturedsignals from the one node by the second node and reported to the serverby the second node.

In yet another embodiment, the server processing unit may be furtheroperative to infer the location of the third node by being operative todetermine a relative location of the third node to the first node or,alternatively, to the second node.

In still another embodiment, context data may be relied upon to refinelocations. More specifically, the server processing unit may be furtheroperative to adjust the inferred location of the third node to determinea refined location of the third node based upon third node context datarelated to the inferred location of the third node.

In a more detailed embodiment, the server memory storage may furthermaintains context data, and the server processing unit may be furtheroperative to triangulate by being operative to access first node contextdata as part of the context data maintained on the server memorystorage, where the first node context data is related to a contextualenvironment near the first node. Likewise, the server processing unitmay be further operative to access second node context data as part ofthe context data maintained on the server memory storage, where thesecond node context data is related a contextual environment near thesecond node. The server processing unit may then be operative to adjustthe determined distance of the one node to the location of the firstnode based upon the first node context data to provide a refineddistance of the one node to the location of the of the first node. Assuch, the server processing unit may be operative to triangulate thelocation of the one node based upon the adjusted determined distance ofthe one node to the location of the first node, the adjusted determineddistance of the one node to the location of second node, and adetermined distance of the one node to the refined location of the thirdnode.

Combined Methods for Determining Node Location

In light of the examples explained above for locating a node, oneskilled in the art will appreciate that a further embodiment expresslycontemplates using more than one of the above-described locationdetermination techniques when determining a refined location of a nodein a wireless node network. For example, such combination embodimentsmay apply an ordered or prioritized approach whereby a first locationtechnique is applied to generate first location information regardingthe location of a node in the wireless network. Thereafter, a secondlocation technique may be selected from a hierarchy or prioritized setof techniques (some of which may work better in certain circumstancesand be chosen or dynamically prioritized based upon the contextualenvironment), and applied to generate second location informationregarding the location of the node or refining the location of the node.Other embodiments may apply additional location techniques to generatefurther refined location information.

In an embodiment, the information in the exemplary hierarchy generallyidentifies which technique may be preferred to be used initially as wellas a ranked grouping or listing of when to apply other locationtechniques. Such information in the exemplary hierarchy may be fixed(based upon successful historic data and experience) or be dynamicallyaltered over time as nodes may move relative to each other and, forexample, based upon context data that provides more information relativeto the a current or anticipated contextual environment.

Environmental Anomaly Detection & Responsive Mediation Actions

Leveraging these types of hierarchical node elements and their abilityto associate, locate, and communicate as part of a further exemplarywireless node network, a variety of additional embodiments involvenode-based technical solutions that enhance and improve how to detectand automatically react to dangerous conditions due to an environmentalanomaly, such as a fire, explosion, chemical leak, radiation leak, or acombination of such environmental conditions indicative of amulti-faceted environmental anomaly. Detecting such an environmentalanomaly and automatically generating an alert that selectively initiatesdifferent types of mediation responses may be performed in the contextof packages being transported in a shipping container on a transitvehicle (such as an aircraft). As such, those skilled in the art willappreciate that the above described basics of a wireless node networkmay be used and extended as parts of embodiments of systems, apparatus,and methods described below for improved environmental anomalydetection, related enhanced layered alerting of particularly targetedmediation recipients, and initiating different types of mediationresponses to such an environmental anomaly using one or more elements ofan adaptive, context-aware wireless node network.

In general, FIGS. 24A-24C illustrated various general examples ofsystems using an exemplary wireless node network of elements fordetecting environmental anomalies. In more detail, FIG. 24A is a diagramof an exemplary wireless node network used for detecting environmentalanomalies using a command node and multiple ID nodes disposed within ashipping container in accordance with an embodiment of the invention.Referring now to FIG. 24A, an exemplary system 24000 is illustrated formonitoring a shipping container 24300 being transported by a transitvehicle 24200 within transit vehicle storage 24205 of the vehicle. Theshipping container 24300 is shown as maintaining packages 24400 a-24400c and is being monitored by system 24000 for an environmental anomalyusing a wireless node network. Such a system 24000 has multiple ID nodes24120 a-24120 c disposed within the shipping container 24300 along witha command node 24160 mounted to and associated with the shippingcontainer 24300. In some embodiments, each of the ID nodes 24120 a-24120c may be implemented with at least one environmental sensor (e.g.,sensors 360). However, in other embodiments, ID nodes 24120 a-24120 cneed not include sensors as the command node may be monitoring thefunction of particular ID nodes (rather than sensor data generated bythe ID node) as part of detecting an environmental anomaly.

In some embodiments, each of the ID nodes 24120 a-24120 c may bespecifically associated with one of the packages 24400 a-24400 cmaintained within the shipping container 24300 (e.g., travel with one ofthe packages, be affixed to the outside or inside of one of thepackages, or be integrated as part of one of the packages). However, inother embodiments, ID nodes 24120 a-24120 c need not be specificallypart of or associated with a particular one of packages 24400 a-24400 cand, instead, be disposed at different locations within shippingcontainer 24300.

The command node 24160 is a type of master node that may be implementedwithout self-location circuitry (e.g., GPS location circuitry 475), butsome embodiments of command node 24160 may be implemented as a masternode 110 a capable of self-locating as described above. As such and inembodiments involving detecting an environmental anomaly, command node24160 is operative to communicate with each of the ID nodes 24120a-24120 c within container 24300 as well as an external transceiver24150 disposed within and associated with transit vehicle 24200.

In some embodiments, external transceiver 24150 may be implementedwithout being associated specifically with transit vehicle 24200. Forexample, an example of external transceiver 24150 may be implemented bya handheld wireless communication device (e.g., exemplary user accessdevices 200, 205 as explained above that may be implemented by acomputer, a laptop computer, a tablet (such as an Apple iPad®touchscreen tablet), a personal area network device (such as aBluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 24105 with remote server 24100, over a wiredor wireless communication path to command nodes and ID nodes describedherein). Further, exemplary external transceiver 24150 may be a mobiletype of device intended to be easily moved (such as a tablet orsmartphone), and may be a non-mobile type of device intended to beoperated from a fixed location (such as a desktop computer disposed ontransit vehicle 24200).

As explained in more detail below, embodiments of the externaltransceiver 24150 may receive alert notifications from the command node24160, and automatically respond to such alerts by initiating amediation response related to a particular mediation action based uponthe particular environmental anomaly detected. Some responses may havethe external transceiver 24150 triggering a fire suppression system ontransit vehicle 24200 and/or communicating with an operator or logisticscrew aboard transit vehicle 24200 using a display interface on thetransceiver (e.g., an LCD display for the operator or crew, a touchscreen display, status lights, speaker) and user input interface on thetransceiver (e.g., a touchscreen interface, buttons, keys, switches,microphone, or other feedback input devices). Further, externaltransceiver 24150 may communicate with remote control center server24100 over network 24105 to report the detected environmental anomalyand any mediation response initiated as well as to receive informationabout the packages 24400 a-24400 c, environmental threshold conditionsrelated to such packages, and other updated data to be used fordetecting environmental anomalies and initiating responsive mediationactions. As such, prompted messages and user input about anyenvironmental anomaly may take the form of visual, audible, orelectronic form (e.g., a prompted message on a visual screen on externaltransceiver 24150, a sound alert message as the prompt, or an electronicmessage about the anomaly and/or responsive mediation actions beinginitiated).

In further embodiments, command node 24160 may be able to send the alertnotification directly to onboard systems (such as a display in a cockpitor logistics support area of a transit vehicle 24200, or an onboard firesuppression system on the transit vehicle 24200) without needing toinvolve an intermediary separate external transceiver that receives thealert notification and responds by initiating a mediation action bycommunicating with such onboard systems. In this manner, someembodiments may deploy an exemplary onboard system involved with themediation action where that system may be considered to have a built-incommunication interface that may operate as a type of externaltransceiver with which to communicate with the command node 24160 of aparticular shipping container 24300. Additional embodiments may alsodeploy transceiver 24150 as being internal to the shipping container ormay have the command node and internal transceiver that initiates themediation responsive action being the same node-based transceiverdevice.

As noted above, each of the ID nodes 24120 a-24120 c may be specificallyassociated with a package or may be disposed at different locationswithin shipping container 24300. In more detail, while FIG. 24Aillustrates system 24000 using a command node 24160 and ID nodes 24120a-24120 c disposed within shipping container 24300 in accordance withdifferent embodiments of the invention, FIG. 24B is a diagram ofexemplary system 24005 for detecting environmental anomalies usingcommand node 24160 and ID nodes 24120 a-24120 c as disposed on or withinpackages 24400 d-24400 f being transported within shipping container24300 in storage 24205 of transit vehicle 24200. In this manner, thesensor data generated by each of ID nodes 24120 a-24120 c as deployed insystem 24005 may be sensor data specifically about the interiorenvironmental condition relative to particular packages (i.e., packages24400 d-24400 f) where the sensor data generated by each of ID nodes24120 a-24120 c as deployed in system 24000 may be sensor data moretargeting the environmental conditions next to or outside of particularpackages (i.e., packages 24400 d-24400 f).

Further still, FIG. 24C is a diagram of still another exemplary wirelessnode network implementing an exemplary system 24010 for detectingenvironmental anomalies using command node 24160 and ID nodes 24120a-24120 f that are less focused on particular packages and moregeographically dispersed within a shipping container in accordance withan embodiment of the invention. In this manner, the embodiment shown inFIG. 24C deploys the ID nodes 24120 a-24120 f so as to have different IDnodes in different parts of the shipping container 24300 so that each IDnode may monitor different spatial regions of the shipping container24300.

While FIGS. 24A-24C generally illustrate exemplary transit vehicle24200, those skilled in the art will appreciate that embodiments mayimplement exemplary transit vehicle 24200 as an aircraft, automotivevehicle, a railway conveyance, a maritime vessel, or other roadwayconveyance (e.g., tractor trailer, etc.) that are capable oftransporting containers maintaining packages being shipped. Shipping ofcontainerized groups of packages (e.g., ULD types of containers made tooptimize airborne logistics handling of packages) is an example of wherea mobile storage unit (such as a movable ULD container) may be deployedwhen shipping node packages in an airborne environment. For example,FIG. 25A is a diagram illustrating multiple shipping containers in theform of exemplary ULD containers 24300 a-24300 d, as loaded into a cargostorage of an aircraft in accordance with an embodiment of theinvention. Referring now to FIG. 25, a cut-away perspective view of anexemplary aircraft fuselage 25000 is illustrated. In particular, anexemplary floor 25005 of a cargo storage area (a type of transit vehiclestorage 24205) within fuselage 25000 is shown having multiple rollerelements that help facilitate movement of cargo within the cargo area.Additionally, while not shown in FIG. 25A, the cargo storage area andfloor 25005 typically include structure and fastening points to helphold any cargo loaded within fuselage 25000. The cargo storage areawithin exemplary fuselage 25000 may be split into an upper area and alower area by an additional floor 25008.

The cut-away perspective example illustrated in FIG. 25A shows a lowercargo area where various ULD containers 24300 a-24300 d are shown alongwith an exemplary airborne external transceiver 24150 on the aircraft.Exemplary external transceiver 24150 may be implemented with a masternode or other wireless transceiver external to the ULD containers 24300a-24300 d and be operative to communicate with command nodes within eachof the respective ULD containers 24300 a-24300 d as part of embodimentsthat detect environmental anomalies within such containers. Whileexemplary external transceiver 24150 is shown disposed within the cargostorage area of the aircraft, those skilled in the art will appreciatethat other embodiments may have the external transceiver 24150 disposedin another part of the aircraft (such as in a cockpit area or alogistics support area) so long as it is deployed and configured tocommunicate with command nodes within each of the respective ULDcontainers 24300 a-24300 d. Similar to that shown in FIGS. 24A-24C, theexternal transceiver 24150 illustrated in FIG. 25A may communicate witha remote server (such as remote control center server 24100) locatedoutside the aircraft in order, for example, to report on any detectedenvironmental anomalies and receive updated information about shipmentsor relevant logistics transit information that may be used to helpassess potential mediation response actions to be taken onboard theaircraft.

Further embodiments may have exemplary external transceiver 24150 inoperative communication with other systems onboard the aircraft, such asa fire suppression system that may be automatically triggered fordeployment by the external transceiver 24150 in response to an alertnotification from one or more of the command nodes within ULD containers24300 a-24300 d on the transit vehicle (e.g., the aircraft). FIG. 25B isa diagram illustrating multiple exemplary shipping containers in a cargostorage area of an aircraft having an exemplary fire suppression systemonboard that selectively and responsively deploys as part of a possibletargeted mediation response to a detected environmental anomaly in oneor more of the shipping containers in accordance with an embodiment ofthe invention. Referring now to FIG. 25B, exemplary fire suppressionsystem 25010 is illustrated as having respective deployable firesuppression modules respective to each of ULD containers 24300 a-24300d. Each of the modules of exemplary fire suppression system 25010 may beselectively activated with a signal to a controller that initiatespressurized expulsion of a fire suppression agent from fire suppressionagent reservoir chamber into its respective ULD container. This mayoccur using an articulating puncture that forcibly creates an opening ina surface of the respective ULD container and through which the firesuppression agent may flow into the ULD container so as to address adetected environmental anomaly within that ULD container. A moredetailed embodiment of such an exemplary fire suppression system 25010is described in U.S. Pat. No. 9,901,764 assigned to FedEx Corporation,which is hereby incorporated by reference.

In further embodiments, the exemplary external transceiver may bedisposed in other parts of the aircraft manned by aircraft personnel(e.g., as a pilot operator or logistics support crew personnel) and mayhave one or more displays (e.g., a screen, status light, touchscreen forprompted messages) and user input interfaces (e.g., buttons, switches,keys, and the like for receiving feedback input). FIG. 25C is a diagramillustrating further exemplary external transceivers disposed in variouscontrol compartments of an exemplary aircraft transit vehicle inaccordance with an embodiment of the invention. Referring now to FIG.25C, exemplary aircraft 25100 is generally shown having a cockpitcompartment 25105 in the front of aircraft 25100 and a cargo storagecompartment 25110 within the fuselage of aircraft 25100. In theillustrated embodiment, cargo storage compartment 25100 includes aninterior shipment storage area 25120 (similar to that shown in cutawayview in FIG. 25A) where items/packages to be shipped or transported maybe loaded for transport and where such items are temporarily maintainedduring transport. For example, ULD containers 24300 a, 24300 b are shownsecured within interior shipment storage area 25120. Additionally,palletized packaged shipping items (PSI) 25300 a-25300 d are secured topallet 25150 as another type of shipping container maintained withininterior shipment storage area 25120. In the illustrated embodiment,cargo storage compartment 25110 also includes a logistics support area25115 where logistics support personnel may be located and from wheresuch personnel may be prompted to inspect one or more of the containerswithin area 25120 in response to detecting an environmental anomaly.

Within the cockpit compartment 25105, an embodiment may have a cockpittransceiver 25150 a as a type of external transceiver operative tocommunicate with command nodes in shipping containers on the aircraft(such as ULD containers 24300 a, 24300 b or a command node associatedwith palletized PSI 25300 a-25300 d secured to pallet 25150). As such,the command node of a particular shipping container may generate alayered alert notification to the cockpit transceiver 25150 a thatidentifies the pilot operator working in cockpit compartment 25105 as atargeted mediation recipient to be notified about a particular detectedenvironmental anomaly with a shipping container. Similarly, anembodiment may alternatively or also have a logistics transceiver 25150b as a type of external transceiver operative to communicate withcommand nodes in shipping containers on the aircraft (such as ULDcontainers 24300 a, 24300 b or a command node associated with palletizedPSI 25300 a-25300 d secured to pallet 25150). As such, the command nodeof a particular shipping container may generate a layered alertnotification to the logistics transceiver 25150 a that identifies thelogistics crew working in logistics support area 25115 as a targetedmediation recipient to be notified about a particular detectedenvironmental anomaly with a shipping container. These type of alertnotifications sent by the command node to the cockpit/logisticstransceiver initiate a mediation response to what the command nodeidentifies to be a targeted mediation action as will be explained inmore detail below. Such mediation response may, for example, generate aprompt that requests for a change in course for the aircraft and/or arequest to investigate a particular shipping container.

As noted above with respect to FIGS. 24A-24C, an exemplary command node,such as command node 24160 mounted to and associated with shippingcontainer 24300, may be implemented as a type of master node. FIG. 26 isa more detailed diagram of an exemplary command node device inaccordance with an embodiment of the invention where components of thecommand node device are shown as disposed within a command nodeenclosure for housing such a device. Referring now to FIG. 26, thoseskilled in the art will appreciate that one embodiment of exemplarycommand node 26000 includes many of the same hardware, code, and datacomponents as shown for exemplary master node 110 a of FIG. 4 (includingcontext data maintained within memory 26415 and 26420), but simplifiedso as not to include location circuitry. As such, similar functionalityexists for what is numbered the same and described above regardingexemplary master node 110 a of FIG. 4. Thus, while master node 110 ashown in FIG. 4 includes processing unit 400, memory storage 415,volatile memory 420, clock/timer 460, sensors 465, battery/powerinterface 470, short range communication interface 475, and medium/longrange communication interface 480, exemplary command node 26000 may usesimilar hardware components as shown in FIG. 26 including processingunit 26400, memory storage 26415, volatile memory 26420, clock/timer26460, sensors 26465, battery/power interface 26470, short rangecommunication interface 26475, and medium/long range communicationinterface 26480. Additionally, an alternative embodiment of command node26000 may include location circuitry to enable the command node toself-locate using circuitry similar to that described with locationcircuitry 475 on master node 110 a and shown in FIG. 4. Also, anotherembodiment of command node 26000 may be implemented as a master nodeseparately from the shipping container but being mounted to the shippingcontainer.

Notably, an embodiment of exemplary command node 26000 illustrated inFIG. 26 deploys command node (CN) control and management code 26425 (asstored in memory storage 26415 and loaded for execution by processingunit 26400 in volatile memory 26420), which is similar in functionalityto master node control and management code 425 described above in moredetail. Essentially, CN control and management code 26425 operatessimilar to that as described above for master node control andmanagement code 425 but may also include program code for improvedmonitoring for an environmental anomaly as described in more detailbelow. Thus, in the illustrated embodiment, such further program code isimplemented as an integrated part of CN control and management code26425, such as one or more programmatic functions or additional programmodules within code 26425. But in other embodiments, the further programcode used to implement the methods and functionality as described for acommand node below may be implemented separately from code 26425. Assuch, the collective code executing on a command node, such as exemplarycommand node 26000 (or any of the other implementations of a commandnode as described herein), acts to programmatically configure thecommand node beyond that of a generic processing device in order to bespecially adapted, via such program code, to be operative to functionunconventionally—whether alone with the specific functionality describedherein or as part of a system.

Command node 26000 (and embodiments based upon such an exemplary commandnode) may receive updates to is CN control and management code 26425(including any program code related to the functionality as set forth inthe embodiments described herein that improves or enhances monitoringfor, detecting, and responding to a detected environmental anomaly). Forexample, an exemplary command node (such as command node 26000 orcommand node 24160) may receive updates of such code (or other data usedon the command node) from external transceiver 24150, which may havereceived the updated code for the command node from remote controlcenter server 24100. Such updates may be sent to the exemplary commandnode or, alternatively, the command node may download the updatesperiodically.

An embodiment of the exemplary CN control and management code 26425 thatprovides for improved monitoring for an environmental anomaly asdescribed in more detail below may also include rules for managing whichof its two different communication interfaces to use when communicatingwith the facility master node. In some embodiments, command node 26000may have node processing unit communicating with external transceiver24150 over the medium/long range communication interface 26485 becausethe distance between the external transceiver 24150 and command node26000 (e.g., command node 24160 as shown in FIGS. 24A-24C) may be toofar for effective communications using the short range communicationinterface 26480. As such, the effective communication range between thenodes may be a factor considered by the processing unit 26400 withincommand node 26000 when determining how to accomplish communicating withthe facility master node 37110 a.

However, when the range between the command node 26000 and externaltransceiver 24150 is close enough to where the command node 26000 mayuse either interface to established communications with the externaltransceiver 24150, other factors may be considered when determiningwhich interface on the command node to use, such as relative congestionof data communications on the short range modes of communication versusthe longer range mode of communication.

In another embodiment, command node 26000 may depend upon themedium/long range communication interface 26480 when node-to-nodecommunications may not be possible with the short range communicationinterface 26485. For example, a ULD having a command node may be loadedon an aircraft where the external transceiver may not have an operatingshort range communication interface. As such, command node 26000 isoperative to determine which of the communication interfaces to use, andbroadcast messages to and received messages from the externaltransceiver using an appropriate one of the two communication interfacesonboard the command node 26000.

As described above, exemplary command node 26000 may use data andsoftware components as shown in FIG. 26 similar to that used by a masternode, including context data as a type of shared data. For example andas shown in FIG. 26, exemplary command node 26000 may locally maintaincontext data 26560 within memory storage 26415 and volatile memory26450. Those skilled in the art will appreciate that context data 26560as used on a command node may be stored and maintained as a separatedata structure, as shown in FIG. 26, but may also be part of shared data445 (as context data may be considered a type of shared data for localuse and storage on a particular node).

As explained in more detail below, such context data 26560 used with acommand node may be related to packages (e.g., environmental thresholdconditions related to a particular package, group of packages, or ashipment container generally) and may be updated by other networkdevices (such as an external transceiver or remote control centerserver) or manually updated by interactions with such network devices bylogistics personnel or transit vehicle operators or pilots. Additionalembodiments described below may have context data 26560 used with acommand node as being container status data related to a particularshipping container, vehicle status data, geolocation data (also a typeof location data 455), or facility status data on a storage facility forthe shipping container. Furthermore, an embodiment may have context data26560 as being relative location data (another type of location data455) indicating a relative location of a package in the container basedon when in the container load cycle that package was processed.

Additionally, exemplary command node 2600 may use one or more of its ownsensor or sensors 25465, which may be monitored in addition to what ismonitored from the ID nodes within or near the command node's shippingcontainer when attempting to detect potential environmental anomalies.Thus, while some embodiments may have the command node rely on what is(or is not) broadcast from particular ID nodes when identifying anddetecting an environmental anomaly related to the command node'sshipping container, further embodiments may deploy the command node'sown onboard sensor as part of this monitoring, identification, anddetection scheme.

In summary, such an exemplary command node 26000 may function in aparticularly programmed and collectively unconventional manner to add afurther management layer within an exemplary wireless node network usedto monitoring a shipping container for an environmental anomaly andresponsively help initiate an automate and layered response that morequickly addresses any detected environmental anomaly.

Multi-Sensor Monitoring for an Environmental Anomaly & Layered AlertGeneration

In light of the description above related to different wireless nodenetwork elements, their operation, interconnections and interoperabilityas part of systems, and the above general description of embodimentsthat may deploy of such network elements when detecting an environmentalanomaly related to a shipping container (whether during transport,loading for transport, unloading after transport, or during otherlogistics operations involving such a shipping container), additionaldetailed information about several embodiments described below focus onuse of signals and sensor data gathered from multiple sensor-based IDnodes within a container as part of monitoring a shipping container foran environmental anomaly. In general, the ID nodes may be travelingwithin packages, but some embodiments may the ID nodes affixed to theoutside of the packages, integrated within the packing materials of thepackages, or may deploy the ID nodes within the container but notspecifically associated with any particular one of the packages in thecontainer. In these embodiments, the ID nodes may provide theirrespective sensor data to the command node, which has the monitoringresponsibility beyond just a single sensor data threshold. Depending onthe particular embodiment, the command node for the container may alsohave its own sensor or sensors to use as part of identifying anddetecting a possible environmental anomaly related to the shippingcontainer. As explained below, such exemplary sensor data may includetemperature, radiation, chemical detection, barometric pressure, and thelike as part of determining if an environmental anomaly exists and torapidly and automatically respond. For example, a sudden change inbarometric pressure may indicate fire or an explosive event. As detailedbelow in the different embodiments, the resulting improved alertgeneration can focus on a type of response needed depending on contextdata regarding what is loaded in the shipping container as well as towhom to send the alert (e.g., a fire suppression system for automaticresponse; a pilot or transit vehicle operator for a quick decisivechange in transit for the vehicle; or a crew operator for investigativeresponse within the vehicle).

In a one system embodiment, the sensor data may be from particular IDnodes that are respectively associated with particular packages in ashipping container. The embodiment more specifically focuses on animproved monitoring system for detecting an environmental anomaly in ashipping container that maintains a multiple packages and for reportinga layered alert notification related to the environmental anomaly to anexternal transceiver unit associated with a transit vehicle (e.g., anaircraft) transporting the shipping container. The system includes atleast a command node and a plurality of ID nodes disposed within theshipping container. Each of the ID nodes are associated with arespective one of the packages maintained within the shipping container(such as that shown in FIG. 24B where each ID node 24120 a-24120 c) areassociated with packages 24400 d-2440 f). Each of the ID nodes has an IDnode processing unit (also commonly referred to as an ID nodeprocessor), an ID node memory coupled to the ID node processing unit(and maintain at least an ID node monitoring program as part of its nodecontrol and management code), and at least one environmental sensorconfigured to generate sensor data related to an environmental conditionof the respective package associated with each of the ID nodes. Each IDnode further includes a wireless radio transceiver (such ascommunication interface 375) coupled to the ID node processing unit,where the wireless radio transceiver is configured to access the sensordata generated by the environmental sensor and broadcast the sensor datain response to a report command from the ID node processing unit whenthe ID node processing unit executes the ID node monitoring program codeas part of its control and management code (e.g., code 325).

The system's command node is mounted to the shipping container. Forexample, in the embodiment shown in FIG. 24B, command node 24160 may beconsidered mounted to the inside or outside of shipping container 24300.Outside of the shipping container exemplary command node 24160 may bepermanently mounted or temporarily mounted (e.g., loaded into a shipmentpouch that may be temporarily attached to the container having thecommand node and other items for the container, such as shipmentpaperwork). When mounted inside the container, the command node 24160may be permanently mounted, temporarily mounted, or integrated as partof shipping container 24300. The system's command node includes at leasta command node processing unit (also commonly referred to as a commandnode processor (e.g., processor 26400 or processor 400 as describedabove)), a command node memory coupled to the command node processingunit, and two communication interfaces. The command node memorymaintains at least a command node container management program code(such as CN control and management code 26425) and context data relatedto each of the ID nodes (such as context data 26560), where the contextdata includes environmental threshold conditions respectivelycorresponding to each of the packages. For example, a certaintemperature threshold may be uses as an environmental thresholdcondition for a package of lithium-ion batteries.

The communication interfaces on the system's command node include afirst communication interface coupled to the command node processingunit (such as short range communication interface 26480), where thefirst communication interface is configured to communicate with each ofthe ID nodes using a first wireless communication format compatible withthe wireless radio transceiver on each of the ID nodes. A secondcommunication interface on the command node (such as medium/long rangecommunication interface 26485) is coupled to the command node processingunit and configured to communicate with the external transceiver unitassociated with a transit vehicle using a second wireless communicationsformat.

During operation of this system embodiment, the command node processingunit of the command node is programmatically configured, when executingthe command node container management program code, to be operative todetect the sensor data broadcasted from the ID nodes using the firstcommunication interface. For example, the sensor data broadcast by eachof ID nodes 24120 a-24120 c shown in FIG. 24B are detected by commandnode 24160, which then compares the detected sensor data from each ofthe ID nodes and the context data related to each of the ID nodes. Thecommand node then is operative to detect the environmental anomaly forthe shipping container 24300 when the comparison of the detected sensordata and the context data indicates an environmental condition for atleast one of the packages 24400 d-24400 f exceeds its respectiveenvironmental threshold condition. The command node is then operative togenerate a layered alert notification related to the environmentalanomaly for the shipping container in response to detecting theenvironmental anomaly, where the layered alert notification identifies atargeted mediation recipient, identifies a targeted mediation action,and establishes a mediation response priority based upon the comparisonof the received sensor data and the context data; and cause the secondcommunication interface to transmit the layered alert notification tothe transceiver unit to initiate a mediation response related to thetargeted mediation action.

Such a system embodiment may have the command node detecting theenvironmental anomaly based upon relative changes in the environmentalsensor data. For example, in a more detailed embodiment, the commandnode processing unit in command node 24160 may be furtherprogrammatically configured to detect the environmental anomaly for theshipping container 24300 when the comparison of the detected sensor dataand the context data indicates a relative change in the environmentalcondition for the at least one of the packages 24400 d-24400 f exceedsits respective environmental threshold condition.

In another more detailed embodiment, the command node processing unit incommand node 24160 may be further programmatically configured to comparethe detected sensor data and the context data by comparing a relativechange in the detected sensor data from at least one of the ID nodes24120 a-24120 c and the context data locally maintained in the commandnode memory of command node 24160 for that one of the ID nodes 24120a-24120 c. Here, the environmental threshold condition for theparticular package with that one of the ID nodes 24120 a-24120 ccomprising a threshold relative environmental change condition that whenexceeded is indicative of the environmental anomaly for the shippingcontainer 24300. As such, the command node processing unit is furtherprogrammatically configured to detect the environmental anomaly for theshipping container when the comparison of the detected sensor data andthe context data indicates the environmental condition for that package(or set of packages associated with those of the ID nodes) exceeds thethreshold relative environmental change condition.

In more detail, the system described above may have each of the ID nodesbeing further operative to incrementally generate the sensor data over atime period using the environmental sensor on each of the respective IDnodes. As such, the command node processing unit of the system's commandnode 24160 may be further programmatically configured to monitor thegenerated sensor data from each of the ID nodes 24120 a-24120 c over thetime period to identify relative changes in the generated sensor dataover the time period; compare the identified relative changes in thegenerated sensor data and the context data 26560 locally maintained onthe command node memory related to those of the ID nodes 24120 a-24120 cthat are related to the relative changes in the generated sensor data(where the context data 26560 in the command node memory includes atleast relative environmental threshold conditions respectivelycorresponding to each of the packages 24400 d-24400 f); and detect theenvironmental anomaly for the shipping container when the comparison ofidentified relative changes in the generated sensor data and the contextdata related to those of the ID nodes 24120 a-24120 c that correspond tothe identified relative changes in the generated sensor data indicates achanged environmental condition for at least one of packages 24400d-24400 f that exceeds its respective relative environmental thresholdcondition. In this more detailed embodiment of the system, the mediationresponse priority is based upon the comparison of the identifiedrelative changes in the generated sensor data and the part of contextdata 26560 related to those of the ID nodes 24120 a-24120 c thatcorrespond to the relative changes in the generated sensor data.

In more detail, the environmental sensor for a first of the ID nodes24120 a may be implemented with a temperature sensor and theenvironmental sensor for a second of the ID nodes 24120 b may beimplemented with a barometric pressure sensor. With these types ofsensors deployed on ID nodes 24120 a and 24120 b, the command nodeprocessing unit of command node 24160 may be further programmaticallyconfigured to detect the environmental anomaly when: (a) the sensor datadetected from the first ID node 24120 a comprises a temperature value;(b) the sensor data detected from the second ID node 24120 b comprises abarometric pressure value; (c) the temperature value indicates theenvironmental condition of the first package 24400 d associated with thefirst ID node 24120 a exceeds the environmental threshold condition forthe first package 24400 d according to the context data 26560 for thefirst package 24400 d; and (d) the barometric pressure value indicatesthe environmental condition of a second package 24400 e associated withthe second of the ID nodes 24120 b exceeds the environmental thresholdcondition for the second package 24400 e according to the context data26560 for the second package 24400 e.

In another embodiment, the system may have the environmental sensor fora first of the ID nodes 24120 a being a temperature sensor and theenvironmental sensor for a second of the ID nodes 24120 b being one froma group consisting of a barometric pressure sensor, a radiation sensor,and a chemical sensor. In such an embodiment, the command nodeprocessing unit for the system's command node 24160 may be furtherprogrammatically configured to detect the environmental anomaly when:(a) the sensor data detected from the first of the ID nodes 24120 acomprises a temperature value; (b) the sensor data detected from thesecond of the ID nodes 24120 b comprises an environmental conditionvalue of one of a sensed barometric pressure level by the barometricsensor, a detected radiation level by the radiation sensor, or adetected chemical by the chemical sensor; (c) the temperature valueindicates the environmental condition of a first package 24400 dassociated with the first of the ID nodes 24120 a exceeds theenvironmental threshold condition for the first package 24400 daccording to the context data 26560 for the first package 24400 d; and(d) the environmental condition value indicates the environmentalcondition of a second package 24400 e associated with the second of theID nodes 24120 b exceeds the environmental threshold condition for thesecond package 24400 e according to the context data 26560 for thesecond package 24400 e. In such an embodiment, the detected chemical maybe indicative of an explosive, fire, or one of either CO or CO₂.

In still another system embodiment, the environmental sensor for one theID nodes 24120 a-24120 c may have multiple sensor elements, where suchsensor elements include at least a temperature sensor element and abarometric pressure sensor element.

In a system embodiment where the environmental sensors include atemperature and pressure sensor, various types of environmentalanomalies may be identified based on the environmental sensor data aswell as context data for the particular packages (e.g., particularthresholds related to such environmental type of conditions). Forexample, the command node 24160 may be operative to detect theenvironmental anomaly for shipping container 24300 as a fire within theshipping container 24300 when the temperature value exceeds atemperature threshold maintained by the command node 24160 in thecommand node memory as part of the context data 26560 for the firstpackage 24400 d and when the barometric pressure value exceeds apressure threshold maintained by the command node 24160 in the commandnode memory as part of the context data 26560 for the second package24400 e. In another example, the command node 24160 may be operative todetect the environmental anomaly for shipping container 24300 as anexplosion within the shipping container 24300 when the temperature valueexceeds a temperature threshold maintained by the command node 24160 inthe command node memory as part of the context data 26560 for the firstpackage 24400 d and when the barometric pressure value is below apressure threshold maintained by the command node 24160 in the commandnode memory as part of the context data 26560 for the second package24400 e. In yet another example, the command node 24160 may be operativeto detect the environmental anomaly for shipping container 24300 as anexplosion within the shipping container 24300 when the temperature valueexceeds a temperature threshold maintained by the command node 24160 inthe command node memory as part of the context data 26560 for the firstpackage 24400 d and when the barometric pressure value drops faster thana pressure drop threshold maintained by the command node 24160 in thecommand node memory as part of the context data 26560 for the secondpackage 24400 e.

Further still, in an additional system embodiment where theenvironmental sensors include temperature and chemical detectors, thecommand node 24160 may be operative to detect the environmental anomalyfor shipping container 24300 as a detected chemical related fire withinthe shipping container 24300 when the temperature value exceeds atemperature threshold maintained by the command node 24160 in thecommand node memory is part of the context data 26560 for the firstpackage 24400 d and when the detected chemical matches a predeterminedchemical profile maintained by the command node 24160 in the commandnode memory as part of the context data 26560 for the second package24400 e.

Additionally, in a further system embodiment where the environmentalsensors include temperature and radiation detectors, the command node24160 may be operative to detect the environmental anomaly for shippingcontainer 24300 as a radiation leak within the shipping container 24300when the temperature value exceeds a temperature threshold maintained bythe command node 24160 as part of the context data 26560 for the firstpackage 24400 d and when the detected radiation matches a predeterminedradiation profile maintained by the command node 24160 as part of thecontext data 26560 for the second package 24400 e.

A further feature in such a system embodiment may include the ability toselectively set and adjust rates for obtaining sensor data from IDnodes. This can help with following up on potentially spreading orworsening environmental anomalies. For example, in a further systemembodiment, each of the ID nodes may broadcast their respectivelygenerated sensor data by transmitting such sensor data according to abroadcast profile maintained by each of the ID nodes. Such a broadcastprofile (e.g., part of profile data 330 for a particular ID node, suchas any of ID nodes 24120 a-24120 c) defines a first messaging rate usedto regulate how often the generated sensor data is transmitted to thecommand node 24160, where the first messaging rate is higher than adefault messaging rate. The command node 24160 may then instruct each ofthe ID nodes 24120 a-24120 c to broadcast future generated sensor dataat a rate different from the default messaging rate after transmittingthe layered alert notification to the transceiver unit—e.g., changingfrom the default messaging rate to the higher first messaging rate, orchanging to a second messaging rate that exceeds the first messagingrate. Such a first messaging rates may be an initial value correlated toan environmental risk associated with at least one of the packageswithin the shipping container. Likewise, the second messaging rate maybe a predetermined messaging rate based upon a type of material existingwithin at least one of the packages within the shipping container (e.g.,a rate that is higher than other rates due to the character of what isbeing transported in package 24400 a, such as lithium-ion batteries orother materials having transport risks associated with them).

In the system embodiment, the layered alert notification generated andbroadcast by the command node identifies a targeted mediation recipientfor such an alert. In more detail, the command node may be furtherprogrammatically configured to automatically select the targetedmediation recipient based upon an excess condition on how much thedetected sensor data and the context data indicates the environmentalcondition for the at least one of the packages exceeds the environmentalthreshold condition for the at least one of the packages. For example,the targeted mediation recipient identified by the command node 24160 inthe layered alert notification may be a triggered fire suppressionsystem on the transit vehicle (e.g., exemplary fires suppression system25010 within an aircraft as shown and explained in FIG. 25B) that isoperative to automatically respond to the detected environmental anomalybased upon receipt of the layered alert notification. Such a triggeredresponse may involve deploying fire suppression material within theshipping container 24300 having the command node 24160 sending thelayered alert notification. In another example, the targeted mediationrecipient identified by the command node 24160 in the layered alertnotification may be an operator of the transit vehicle (e.g., pilot ofthe aircraft) that can alter movement of the transit vehicle. In stillanother example, the targeted mediation recipient identified by thecommand node 24160 in the layered alert notification may be a logisticscrew member of the transit vehicle that can inspect the shippingcontainer 24300. In like manner, the targeted mediation response in thelayered alert notification may be an automatic response to be performedby a triggered fire suppression system on the transit vehicle, a requestto change course of the transit vehicle from an existing travel path ofthe transit vehicle (displayed on a screen of, for example, cockpittransceiver 25150 a to a pilot/operator), and/or a request toinvestigate the shipping container (displayed on a screen of, forexample, logistics transceiver 25150 b to logistics crew member).

In the system embodiment, the layered alert notification generated andbroadcast by the command node also identifies a targeted mediationaction as part such an alert. In more detail, the targeted mediationaction may be automatically selected by the command node 24160 basedupon an excess condition on how much the detected sensor data from theID nodes 24120 a-24120 c and the context data 26560 indicates theenvironmental condition for at least one of the packages 24400 d-24400 fexceeds the environmental threshold condition for that one of thepackages. In another example, the targeted mediation action identifiedby the command node 24160 in the layered alert notification depends uponwhat is loaded within the shipping container 24300 as indicated byshipping information maintained on the command node 24160 (e.g.,shipment data (similar to shipment data 580) maintained as part ofcontext data 26560 in memory of command node 24160). In still anotherexample, the targeted mediation action identified by the command node24160 in the layered alert notification depends upon an excess conditionon how many of the packages 24400 d-24400 f have their detected sensordata and their context data indicating that their environmentalcondition exceed the environmental threshold condition for the packages24400 d-24400 f Thus, as more packages have exceeded their respectiveenvironmental threshold conditions, the command node 24160 may shiftwhat the appropriate targeted mediation action is identified to be aspart of the layered alert notification.

In some embodiments, the targeted mediation action may depend uponfurther types of context information or data. As described above,exemplary context data 26560 may include container status data relatedto a particular shipping container, vehicle status data, geolocationdata (also a type of location data 455), or facility status data on astorage facility for the shipping container. As such, a further systemembodiment may have the command node processing unit of the system'scommand node (e.g., command node 24160) further programmaticallyconfigured to receive vehicle status data from the external transceiverunit 24150 of the transit vehicle 24200 using the second communicationinterface and maintain the vehicle status data in the command nodememory as part of context data 26560, and where the targeted mediationaction identified in the layered alert notification depends upon a stateof the transit vehicle 24200 as indicated by the vehicle status data.The state or status of the vehicle indicated by the vehicle status datamay, for example, be a takeoff vehicular status, a cruising vehicularstatus, a landing vehicular status, and an on-the-ground vehicularstatus. In another example, the command node memory may maintaincontainer status data as part of context data 26560, where suchcontainer status data container information corresponding to the stateof a shipping container (such as ULD container 24300). As such, thetargeted mediation action in the layered alert notification sent bycommand node 24160 can depend upon a state of the shipping container asindicated in the container status data.

As noted with respect to exemplary command node 2600, an embodiment ofsuch a command node may include location circuitry (similar to thatshown as location circuitry 475 with master node 110 a) that is coupledto the command node's processor 26400. Such location circuitry isoperative to detect geolocation data related to a current location ofthe shipping container within the transit vehicle, such that a furtherembodiment may have the targeted mediation action identified in thelayered alert notification depending upon the current location of theshipping container as indicated in the geolocation data.

In a further system embodiment, the command node may maintain loadingplan data indicating the relative location of the command node'sshipping container within the transit vehicle. For example, command node24160 may having loading plan data as part of its context data 26560 andsuch loading plan data may indicate the relative location of ULDcontainer 24300 within the storage 24205 of transit vehicle 24200. Assuch, a further system embodiment may have the targeted mediation actionidentified by command node 24160 in the layered alert notificationbroadcast by command node 24160 depending upon the relative location ofULD container 24300 within the transit vehicle 24200 as indicated in theloading plan data within context data 26560 on command node 24160.

In still a further system embodiment, the command node may maintainfacility status data associated with a storage facility for the shippingcontainer (such as facility status data associated with an aircrafthangar used by an aircraft, a logistics depot used by a delivery vehicleor other storage facility that may temporarily be used by the shippingcontainer). For example, command node 24160 may having facility statusdata as part of its context data 26560 and the targeted mediation actionidentified by command node 24160 in the layered alert notificationbroadcast by command node 24160 depending upon the state of the storagefacility as indicated in the facility status data.

The layered alert notification generated by the system's command nodealso identifies a mediation response priority based upon the comparisonof the received sensor data and the context data. In a more detailedembodiment, the mediation response priority may be automaticallyselected by the command node processing unit when generating the layeredalert notification based upon an excess condition on how much thedetected sensor data and the context data indicates the environmentalcondition for the at least one of the packages exceeds the environmentalthreshold condition for the at least one of the packages. Thus, forexample, when the sensor data indicated an environmental condition forat least one of the packages in the container far exceeds the respectiveenvironmental threshold condition for that package (which may indicate afire or explosive event), the mediation response priority established bythe command node as part of the layered alert notification may be a highpriority level indicating further travel by the transit vehicle is to beat least minimized when responding to the detected environmentalanomaly. In another example, the mediation response priority establishedby the command node as part of the layered alert notification may be anintermediate priority level indicating further travel by the transitvehicle is permissible when responding to the detected environmentalanomaly.

A further embodiment of this system may selectively use particular IDnodes when monitoring for the environmental anomaly. In such a furtherembodiment, the command node processing unit of the system's commandnode may be further programmatically configured to select each of the IDnodes from a larger group of network elements being loaded into theshipping container. For example, command node 24160 may select only IDnodes 24120 a and 24120 c within shipping container 24300 as shown inFIG. 25B. The ID nodes selected provide the gathered sensor data for usein detecting the environmental anomaly for the shipping container 24300as described above. In more detail, the command node processing unit maybe further programmatically configured to identify each of the ID nodesselected based upon package content information and/or loading plan datamaintained within the command node memory (e.g., package contentinformation and loading plan data being part of exemplary context data26560 maintained on command node 24160).

Another further embodiment of this system may remotely alter thresholdlimits as part of improving the responsive mediation. In such a furtherembodiment, the command node processing unit of the system's commandnode may be further programmatically configured to receive an update forthe environmental threshold conditions for at least one of the packagesusing the second communication interface. Such an update may come fromthe external transceiver unit over the second communication interface ofthe command node. The update for the environmental threshold conditionsmay be defined by an operator of the transit vehicle using the externaltransceiver unit (e.g., cockpit transceiver 25150 a shown in FIG. 25C)or a logistics crew member of the transit vehicle using the externaltransceiver unit (e.g., logistics transceiver 25150 b shown in FIG.25C). Further, such an update for the environmental threshold conditionsmay be provided to the external transceiver unit from a remote controlcenter (e.g., remote control center server 24100 in communication withthe external transceiver unit 24150).

In still a further embodiment of this system, the validity ofcommunications (e.g., broadcasted sensor data) may be confirmed orverified to provide a more secure and robust system that is lesssusceptible to error or spoofing by other nodes. In such a furtherembodiment, the command node processing unit may be programmaticallyconfigured to detect the sensor data using the first communicationinterface by being further operative to: (a) receive the sensor databroadcasted from a first of the ID nodes using the first communicationinterface; (b) confirm the validity of the received sensor data; (c)repeat (a) and (b) for the remainder of the sensor data received fromany of the remaining ones of the ID nodes using the first communicationinterface; and (d) selectively compile the detected sensor data usingonly the received sensor data confirmed valid.

In more detail, the command node may confirm that it uses only validsensor data when detecting an environmental anomaly in an active orpassive manner. In an “active” example, the command node may cause thefirst communication interface to send an authentication request to an IDnode, and receive a validation response from that ID node via the firstcommunication interface. Such an actively requested validation responseauthenticates the sensor data broadcasted from that one of the ID nodes.In a “passive” example, the command node may confirm the validity of thereceived sensor data by being further operative to access a validationsequence for an ID node as maintained by the command node in memory(e.g., as part of security data 435 or profile data 430 on command node26000 for that particular ID node). Such a validation sequencecharacterizes expected broadcasts from that particular ID node. Usingsuch a validation sequence, the command node may then passivelydetermine if the received sensor data from that ID node matches apredetermined one of the expected broadcasts from that ID node withoutthe need to poll or interactively request authentication from that IDnode. In more detail, the predetermined one of the expected broadcastsaccording to the validation sequence may be a rotating value previouslyreceived by the command node for that ID node as a way of enhancingsecurity for the command node to better determine and confirm that IDnode sensor data is coming from a valid ID node and, thus, is validsensor data upon which to make determinations of whether anenvironmental anomaly exists.

Using the above described system embodiment that monitors a shippingcontainer for an environmental anomaly using ID nodes associated withpackages and environmental threshold conditions corresponding to thepackages, a further embodiment focuses on an improved method formonitoring the shipping container using such system elements. FIG. 27 isa flow diagram illustrating an exemplary method for monitoring ashipping container for an environmental anomaly using a wireless nodenetwork using sensor data from ID nodes associated with packages andwith environmental threshold conditions for the packages in accordancewith an embodiment of the invention. In more detail and referring now toFIG. 27, exemplary method 2700 describes an improved method formonitoring a shipping container (e.g., ULD shipping container 24300) foran environmental anomaly using a wireless node network having at least aplurality of ID nodes (e.g., ID nodes 24120 a-24120 c) disposed withinthe shipping container and a command node (e.g., command node 24160)mounted to and associated with the shipping container, each of the IDnodes having at least one environmental sensor and being associated witha respective one of a group of packages (e.g., packages 24400 d-24400 f)maintained within the shipping container, and where the command node isoperative to communicate with each of the ID nodes and an externaltransceiver unit (e.g., external transceiver 24150) associated with atransit vehicle (e.g., transit vehicle 24200, such as an aircraft,railway conveyance, a maritime vessel, or a roadway conveyance). Method2700 begins at step 2705 with the environmental sensor or sensors oneach of the ID nodes generating sensor data related to an environmentalcondition of the respective package associated with each of the ID nodesas the packages reside within the shipping container. In more detailedembodiment, the environmental sensor for a first of the ID nodes may bea temperature sensor while the environmental sensor for a second of theID nodes may be a barometric pressure sensor. In another embodiment, theenvironmental sensor for a first of the ID nodes may be a temperaturesensor while the environmental sensor for a second of the ID nodes maybe one from a group consisting of a barometric pressure sensor, aradiation sensor, and a chemical sensor. In still a further embodiment,the environmental sensor for one or more of the ID nodes may havemultiple sensor elements, where such sensor elements may include atleast a temperature sensor element and a barometric pressure sensorelement (but may also include a radiation sensor and/or a chemicalsensor).

At step 2710, method 2700 proceeds with each of the ID nodesbroadcasting their respectively generated sensor data. At step 2715,method 2700 has the command node detecting the sensor data broadcastedfrom the ID nodes. Method 2700 then proceeds to step 2720 where thecommand node compares the detected sensor data from each of the ID nodesand locally maintained context data related to each of the ID nodes.Such context data (e.g., context data 26560) includes at least aplurality of environmental threshold conditions respectivelycorresponding to the packages. In this way, a particular environmentalthreshold condition for one package may be different than that ofanother package as, for example, the material in one package may becomevolatile at a lower temperature than material in other packages.

At decision step 2725, method 2700 has the command node determining ifan environmental condition for one of the packages exceeds itsrespective environmental threshold condition based upon the comparisonperformed in step 2720. If so, method 2700 proceeds from step 2725directly to step 2730 where the command node detects the environmentalanomaly for the shipping container because the comparison of thedetected sensor data and the context data indicates an environmentalcondition for at least one of the packages exceeds its respectiveenvironmental threshold condition. If not, method 2700 proceeds fromstep 2725 back to step 2705 where the ID nodes generate more sensor dataand the ID nodes continue to broadcast newly generated sensor data atstep 2710 for detection and consideration by the command node in steps2715-2725 again.

In steps 2725-2730, the command node may detect different types ofenvironmental anomalies depending on the type of sensor data beingconsidered. For example, a further embodiment of method 2700 may havethe command node detecting the environmental anomaly as part of steps2725-2730 when (a) the sensor data detected from one of the ID nodescomprises a temperature value; (b) the sensor data detected from asecond of the ID nodes comprises a barometric pressure value; (c) thetemperature value indicates the environmental condition of a firstpackage associated with the first ID node exceeds the environmentalthreshold condition for the first package according to the context datafor the first package; and (d) the barometric pressure value indicatesthe environmental condition of a second package associated with thesecond ID node exceeds the environmental threshold condition for thesecond package according to the context data for the second package.

Still further embodiments of method 2700 may use a combination oftemperature and other types of sensors. For example, another embodimentof method 2700 may have the command node detecting the environmentalanomaly as part of steps 2725-2730 when (a) the sensor data detectedfrom one of the ID nodes comprises a temperature value; (b) the sensordata detected from a second of the ID nodes comprises an environmentalcondition value of one of a sensed barometric pressure level by thebarometric sensor, a detected radiation level by the radiation sensor,or a detected chemical by the chemical sensor (e.g., the detectedchemical by the chemical sensor may be indicative of an explosive, afire, or the presence of either CO or CO₂); (c) the temperature valueindicates the environmental condition of a first package associated withthe first ID node exceeds the environmental threshold condition for thefirst package according to the context data for the first package; and(d) the environmental condition value indicates the environmentalcondition of a second package associated with the second ID node exceedsthe environmental threshold condition for the second package accordingto the context data for the second package.

The environmental anomaly detected in step 2730 of method 2700 may comein a variety of types depending on the type of sensors used as well. Forexample, a further embodiment of step 2730 may have the command nodedetect the environmental anomaly for the shipping container to be a firewithin the shipping container when the temperature value exceeds atemperature threshold maintained by the command node as part of thecontext data for the first package and when the barometric pressurevalue exceeds a pressure threshold maintained by the command node aspart of the context data for the second package. Another embodiment ofstep 2730 may have the command node detect the environmental anomaly forthe shipping container to be an explosion within the shipping containerwhen the temperature value exceeds a temperature threshold maintained bythe command node as part of the context data for the first package andwhen the barometric pressure value is below a pressure thresholdmaintained by the command node as part of the context data for thesecond package. Yet another embodiment of step 2730 may have the commandnode detect the environmental anomaly for the shipping container to bean explosion within the shipping container when the temperature valueexceeds a temperature threshold maintained by the command node as partof the context data for the first package and when the barometricpressure value drops faster than a pressure drop threshold maintained bythe command node as part of the context data for the second package. Afurther embodiment of step 2730 may have the command node detect theenvironmental anomaly for the shipping container to be a detectedchemical related fire within the shipping container when the temperaturevalue exceeds a temperature threshold maintained by the command node aspart of the context data for the first package and when the detectedchemical matches a predetermined chemical profile maintained by thecommand node as part of the context data for the second package. Andstill another embodiment of step 2730 may have the command node detectthe environmental anomaly for the shipping container to be a radiationleak within the shipping container when the temperature value exceeds atemperature threshold maintained by the command node as part of thecontext data for the first package and when the detected radiationmatches a predetermined radiation profile maintained by the command nodeas part of the context data for the second package.

In other embodiments, method 2700 may detect the environmental anomalybased upon relative changes in sensor data when compared to the relevantcontext data on environmental threshold conditions. For example, steps2725 and 2730 may have the command node detecting an environmentalanomaly when the comparison of the detected sensor data and the contextdata in step 2720 indicates a relative change in the environmentalcondition for at least one of the packages and where such a relativechange exceeds its respective environmental threshold condition (whichmay be defined in terms of relative changes in environmental conditions,such as temperature, pressure, and the like). In a more detailedexample, step 2730 may further have the command node comparing arelative change in the detected sensor data from at least one of the IDnodes and the locally maintained context data for that one of the IDnodes, which has the environmental threshold condition for at least thepackage with that ID node as a threshold relative environmental changecondition that when exceeded is indicative of the environmental anomalyfor the shipping container. As such in this example, detecting theenvironmental anomaly for the shipping container in this embodiment ofstep 2730 occurs when the comparison of the detected sensor data and thecontext data indicates the environmental condition for the one of thepackages associated with that ID node exceeds the threshold relativeenvironmental change condition.

At step 2735, method 2700 proceeds with the command node generating alayered alert notification related to the environmental anomaly for theshipping container in response to detecting the environmental anomaly.The layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority based upon the comparison of the receivedsensor data and the context data. In a further embodiment of method2700, the targeted mediation recipient may be automatically selected bythe command node based upon an excess condition on how much the detectedsensor data and the context data indicates the environmental conditionfor at least one of the packages exceeds the environmental thresholdcondition for at least one of the packages. Such a targeted mediationrecipient identified by the command node in the layered alertnotification may be, for example, a triggered fire suppression system onthe transit vehicle (e.g., exemplary fire suppression system 25010 ofFIG. 25B) that is operative to automatically respond to the detectedenvironmental anomaly based upon receipt of the layered alertnotification; an operator of the transit vehicle that can alter movementof the transit vehicle; or a logistics crew member of the transitvehicle that can inspect the shipping container.

In another further embodiment of method 2700, the targeted mediationaction identified by the command node in step 2735 may be automaticallyselected by the command node based upon an excess condition on how muchthe detected sensor data and the context data indicates theenvironmental condition for at least one of the packages exceeds theenvironmental threshold condition for those packages. In more detail,the targeted mediation action identified by the command node in thelayered alert notification may depend upon what is loaded within theshipping container as indicated by shipping information maintained onthe command node or may depend upon an excess condition on how many ofthe packages have their detected sensor data and their context dataindicating that their environmental condition exceed the environmentalthreshold condition for the packages. With such information, the commandnode may identify an appropriate targeted mediation action, such asimmediately deploying the onboard fire suppression system or, instead,identify a threat appropriate action of notifying a logistics personnelto inspect a particular one or group of packages.

The targeted mediation action in step 2735 may be identified by thecommand node using a variety of types of context data so that thetargeted mediation action may be automatically identified with an robustand improved sense of contextual understanding of the situation. Forexample, in a further embodiment, method 2700 may have the command nodereceiving vehicle status data from the external transceiver unitassociated with the transit vehicle, so that the targeted mediationaction identified by the command node in the layered alert notificationmay depend upon a state of the transit vehicle as indicated by thevehicle status data. Such a state of the transit vehicle may include,for example, a takeoff vehicular status, a cruising vehicular status, alanding vehicular status, and an on-the-ground vehicular status. Thus,context data 26560 may include such vehicle status data, which may beused in identifying the targeted mediation action in response todetecting the environmental anomaly.

In another example, an embodiment of method 2700 may have the commandnode accessing container status data maintained by the command node andassociated with the shipping container, so that the targeted mediationaction identified by the command node in the layered alert notificationdepends upon a state of the shipping container as indicated in thecontainer status data. In yet another example, an embodiment of method2700 may have the command node detecting geolocation data related to acurrent location of the shipping container within the transit vehicle,so that the targeted mediation action identified by the command node inthe layered alert notification depends upon the current location of theshipping container as indicated in the geolocation data. In stillanother example, an embodiment of method 2700 may have the command nodeaccessing loading plan data maintained by the command node (where suchloading plan data indicates a relative location of the shippingcontainer within the transit vehicle), so that the targeted mediationaction identified by the command node in the layered alert notificationdepends upon the relative location of the shipping container within thetransit vehicle as indicated in the loading plan data. And in anotherexample, an embodiment of method 2700 may have the command nodeaccessing facility status data maintained by the command node andassociated with a storage facility for the shipping container, so thatthe targeted mediation action identified by the command node in thelayered alert notification depends upon a state of the storage facilityas indicated in the facility status data.

The targeted mediation response identified in step 2735 may also takeseveral forms. For example, a further embodiment may have the targetedmediation response identified by the command node in the layered alertnotification be an automatic response by a triggered fire suppressionsystem on the transit vehicle; a request to change course of the transitvehicle from an existing travel path of the transit vehicle; or arequest to investigate the shipping container.

Likewise, the mediation response priority established by the commandnode as part of step 2735 may take several forms. For example, thecommand node may establish the mediation response priority as part ofstep 2735 by automatically selecting the mediation response prioritybased upon an excess condition on how much the detected sensor data andthe context data indicates the environmental condition for at least oneof the packages exceeds the environmental threshold condition for thepackage(s). In another example, the mediation response priorityestablished by the command node as part of the layered alertnotification may be established as a high priority level indicatingfurther travel by the transit vehicle is to be at least minimized whenresponding to the detected environmental anomaly, or as an intermediatepriority level indicating further travel by the transit vehicle ispermissible when responding to the detected environmental anomaly.

At step 2740, method 2700 proceeds with the command node transmittingthe layered alert notification to the transceiver unit to initiate amediation response related to the targeted mediation action. In thisway, the command node (e.g., command node 24160 as shown in FIG. 24B)automatically and responsively monitors its particular shippingcontainer by means of the ID nodes associated with packages within theshipping container and responsively provides an enhanced type ofnotification in the form of the layered alert notification to thetransit vehicle's external transceiver (e.g., transceiver 24150), whichis used to cause the external transceiver to initiate the identifiedtype of mediation response related to the identified type of targetedmediation action to deal with the detected environmental anomaly in arapid, improved, and more robust manner. Thereafter, method 2700 mayproceed back to step 2705 where further sensor data may be generated byeach of the ID nodes.

Further embodiments of method 2700 may provide more detailed steps aswell as additional steps. For example, in a more detailed embodiment,the ID nodes generate sensor data over a particular time period and thecommand node, as part of step 2715, may monitor the generated sensordata from each of the ID nodes over the time period to identify relativechanges in the generated sensor data over the time period. Thereafter,as part of step 2720, the step of comparing may have the command nodecomparing the identified relative changes in the generated sensor dataand locally maintained context data (e.g., context data 26560) relatedto those of the ID nodes that are related to the relative changes in thegenerated sensor data. Here, the context data stored on the command nodeincludes at least a plurality of relative environmental thresholdconditions respectively corresponding to the different packages.Further, as part of steps 2725 and 2730, the step of detecting theenvironmental anomaly for the shipping container may occur when thecomparison of identified relative changes in the generated sensor dataand locally maintained context data related to those of the ID nodesthat correspond to each of the identified relative changes in thegenerated sensor data indicates a changed environmental condition for atleast one of the packages exceeds its respective relative environmentalthreshold condition. Additionally, as part of step 2735, the commandnode may establish the mediation response priority as being based uponthe comparison of the identified relative changes in the generatedsensor data and the locally maintained context data related to those ofthe ID nodes that correspond to the relative changes in the generatedsensor data.

Another more detailed embodiment of method 2700 may involvesetting/adjusting the rate an ID node generates and broadcasts sensordata as a way to adaptively respond to an initially detectedenvironmental anomaly. For example, step 2710 of broadcasting thegenerated sensor data by the ID nodes may have each of the ID nodestransmitting their respectively generated sensor data according to abroadcast profile maintained by each of the ID nodes, where such abroadcast profile defines a first messaging rate used to regulate howoften the generated sensor data is transmitted to the command node, andwhere the first messaging rate is higher than a default messaging rate.This further embodiment of method 2700 may also have the command nodeinstructing each of the ID nodes to broadcast future generated sensordata at a second messaging rate that exceeds the first messaging rateafter transmitting the layered alert notification to the transceiverunit in step 2740. The first messaging rate for the ID nodes may be setwith an initial value correlated to an environmental risk associatedwith at least one of the packages within the shipping container, and mayadaptively set the second messaging rate for the ID nodes to apredetermined messaging rate based upon a type of material existingwithin at least one of the packages within the shipping container. Thisfurther embodiment of method 2700 may also have the command nodeinstructing each of the ID nodes to change from the default messagingrate to the first messaging rate. In this way, the command node mayadaptively change the messaging rates by which the ID nodes broadcasttheir sensor data depending on the detected environmental anomaly anddepending on context data (e.g., context data 26560) about the makeup ofpackages being transported within the shipping container.

Still another embodiment of method 2700 may involve selectively andadaptively choosing which of the ID nodes available within the shippingcontainer to use when monitoring for an environmental anomaly. Forexample, this further embodiment of method 2700 may have the commandnode select each of the ID nodes used for detecting the environmentalanomaly from a larger group of network elements being loaded into theshipping container. In this way, the ID nodes that are selected arethose chosen by the command node to provide the gathered sensor data foruse in detecting the environmental anomaly for the shipping container.In more detail, the ID nodes selected may be identified for selection bythe command node based upon contents of the packages associated with theID nodes being selectively activated, or based upon a loading scheme forthe shipping container (where such a loading scheme may be maintained inmemory of the command node as loading plan data that may be stored aspart of context data 26560).

Yet another embodiment of method 2700 may involve remote altering andupdating of thresholds and mediation information used for detecting anenvironmental anomaly and how to respond to such an environmentalanomaly. For example, this additional embodiment of method 2700 may havethe command node receiving an update for the environmental thresholdconditions for at least one of the packages. Such an update may bereceived from the external transceiver unit (e.g., transceiver 24150).This update received from the external transceiver may be defined bypersonnel on the transit vehicle (e.g., an operator or logisticspersonnel on the transit vehicle using the particular externaltransceiver unit (such as cockpit transceiver 25150 a or logisticstransceiver 25150 b) using user input interfaces on the transceiver).Alternatively, the update may be received from a remote control center(e.g., remote control center server 24100 in communication with externaltransceiver 24150).

In still a further embodiment of method 2700, the validity ofcommunications (e.g., broadcasted sensor data) may be confirmed orverified to provide a more secure and robust system that is lesssusceptible to error or spoofing by other nodes. In such a furtherembodiment of method 2700, the command node may detect the sensor datain step 2715 by (a) receiving the sensor data broadcasted from a firstof the ID nodes; (b) confirming the validity of the received sensordata; (c) repeat steps (a) and (b) for the remainder of the sensor datareceived from any of the remaining ones of the ID nodes; and (d)compiling the detected sensor data using only the received sensor dataconfirmed valid in sub step (b) of modified step 2715. In more detail,the command node may confirm as part of (b) that it uses only validsensor data when detecting an environmental anomaly in an active orpassive manner. For example, confirming the validity of the receivedsensor data may have the command node actively sending an authenticationrequest to the first of the ID nodes, and receiving a validationresponse back from that ID node that authenticates the sensor databroadcasted from that ID node. In another example, confirming thevalidity of the received sensor data as part of (b) may have the commandnode, in a more passive sense accessing a validation sequence for an IDnode as maintained by the command node in memory (e.g., as part ofsecurity data 435 or profile data 430 on command node 26000 for thatparticular ID node). Such a validation sequence characterizes expectedbroadcasts from that particular ID node. Using such a validationsequence, the command node may then passively determine if the receivedsensor data from that ID node matches a predetermined one of theexpected broadcasts from that ID node without the need to poll orinteractively request authentication from that ID node. Such apredetermined one of the expected broadcasts according to the validationsequence may be a rotating value previously received by the command nodefor that ID node as a way of enhancing security for the command node tobetter determine and confirm that ID node sensor data is coming from avalid ID node and, thus, is valid sensor data upon which to makedeterminations of whether an environmental anomaly exists.

While exemplary method 2700 and the exemplary system described relativeto FIG. 24B has the ID nodes associated with particular packages,another embodiment of a method and system that monitors for anenvironmental anomaly using ID nodes may be deployed where the ID nodesare not required to be associated with particular packages within theshipping container, and where the environmental threshold conditions arerelated to particular ID nodes. This is similar what is described aboverelative to FIGS. 24A and 24C where specific packages are shown, but thesensor data and relevant environmental threshold conditions focus onparticular ID nodes without being tied to specific packages maintainedwithin shipping container 24300.

FIG. 28 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network using sensor data from ID nodes that are disposedwithin the shipping container but are generally not associated withparticular packages and with environmental threshold conditions for theID nodes in accordance with an embodiment of the invention. In moredetail and referring now to FIG. 28, exemplary method 2800 describes animproved method for monitoring a shipping container (e.g., ULD shippingcontainer 24300 as shown, for example in FIG. 24C) for an environmentalanomaly using a wireless node network having at least a plurality of IDnodes (e.g., ID nodes 24120 a-24120 f shown in FIG. 24C) disposed withinthe shipping container and a command node (e.g., command node 24160 ofFIG. 24C) mounted to and associated with the shipping container thatmaintains multiple packages (e.g., packages 24400 a-24400 c of FIG.24C), where each of the ID nodes has at least one environmental sensor,and where the command node is operative to communicate with each of theID nodes and an external transceiver unit (e.g., external transceiver24150 of FIG. 24C) associated with a transit vehicle (e.g., transitvehicle 24200, which may, for example, be an aircraft, railwayconveyance, a maritime vessel, or a roadway conveyance). In general,exemplary method 2800 is similar to method 2700 as described above withvariations to steps 2705, 2720, and 2725 given the difference in thetype of sensor data broadcast by the ID nodes and the type ofenvironmental threshold conditions used by the command node to detectthe environmental anomaly and determine what goes into the relevantlayered alert notification to the external transceiver so as to initiatean appropriate mediation response to the environmental anomaly.

In more detail, method 2800 begins at step 2805 with the environmentalsensor or sensors on each of the ID nodes generating sensor data relatedto an environmental condition proximate the respective ID node asdisposed within the shipping container. In more detailed embodiment, theenvironmental sensor for a first of the ID nodes may be a temperaturesensor while the environmental sensor for a second of the ID nodes maybe a barometric pressure sensor. In another embodiment, theenvironmental sensor for a first of the ID nodes may be a temperaturesensor while the environmental sensor for a second of the ID nodes maybe one from a group consisting of a barometric pressure sensor, aradiation sensor, and a chemical sensor. In still a further embodiment,the environmental sensor for one or more of the ID nodes may havemultiple sensor elements, where such sensor elements may include atleast a temperature sensor element and a barometric pressure sensorelement (but may also include a radiation sensor and/or a chemicalsensor).

In still another further embodiment of method 2800, the ID nodesgenerating sensor data in step 2805 may be in two different groups—oneof which ID nodes that are disposed on the shipping container itself anda second group of the ID nodes are associated with different ones of aplurality of packages disposed within the shipping container. Furtherstill, the ID nodes generating sensor data in step 2805 may be in athird group—namely, ID nodes that are disposed within the shippingcontainer but not affixed to the shipping container itself.

At step 2810, method 2800 proceeds with each of the ID nodesbroadcasting their respectively generated sensor data about theenvironmental condition proximate the particular ID node within theshipping container. At step 2815, method 2800 has the command nodedetecting the sensor data broadcasted from the ID nodes. Method 2800then proceeds to step 2820 where the command node compares the detectedsensor data from each of the ID nodes and locally maintained contextdata related to each of the ID nodes. Such context data (e.g., contextdata 26560) includes at least a plurality of environmental thresholdconditions respectively corresponding to the different ID nodes. In moredetail, the environmental threshold condition for each of the ID nodesmay depend on where a particular ID node is located within the shippingcontainer or what is placed next to each of the ID nodes according to aloading scheme for the shipping container maintained in memory of thecommand node as loading plan data. In another example, the environmentalthreshold condition for each of the ID nodes as indicated by the contextdata may be a dynamic value that changes or is updated (as discussedherein) when what is placed next to each of the ID nodes within theshipping container changes. In this manner, a command node for theshipping container may have the environmental threshold conditions forthe ID nodes within the shipping container being updated, changed, andrevised as the contents of the shipping container changes and as what isin the container is moved or relocated within the shipping container.

At decision step 2825, method 2800 has the command node determining ifan environmental condition for one of the ID nodes exceeds itsrespective environmental threshold condition based upon the comparisonperformed in step 2820. If so, method 2800 proceeds from step 2825directly to step 2830 where the command node detects the environmentalanomaly for the shipping container because the comparison of thedetected sensor data and the context data indicates an environmentalcondition for at least one of the ID nodes exceeds its respectiveenvironmental threshold condition. If not, method 2800 proceeds fromstep 2825 back to step 2805 where the ID nodes generate more sensor dataand the ID nodes continue to broadcast newly generated sensor data atstep 2810 for detection and consideration by the command node in steps2815-2825 again.

In steps 2825-2830, the command node may detect different types ofenvironmental anomalies depending on the type of sensor data beingconsidered. For example, a further embodiment of method 2800 may havethe command node detecting the environmental anomaly as part of steps2825-2830 when (a) the sensor data detected from one of the ID nodescomprises a temperature value; (b) the sensor data detected from asecond of the ID nodes comprises a barometric pressure value; (c) thetemperature value indicates the environmental condition of the first IDnode exceeds the environmental threshold condition for the first ID nodeaccording to the context data for the first ID node; and (d) thebarometric pressure value indicates the environmental condition of thesecond ID node exceeds the environmental threshold condition for thesecond ID node according to the context data for the second ID node.

Still further embodiments of method 2800 may use a combination oftemperature and other types of sensors. For example, another embodimentof method 2800 may have the command node detecting the environmentalanomaly as part of steps 2825-2830 when (a) the sensor data detectedfrom one of the ID nodes comprises a temperature value; (b) the sensordata detected from a second of the ID nodes comprises an environmentalcondition value of one of a sensed barometric pressure level by thebarometric sensor, a detected radiation level by the radiation sensor,or a detected chemical by the chemical sensor (e.g., the detectedchemical by the chemical sensor may be indicative of an explosive, afire, or the presence of either CO or CO₂); (c) the temperature valueindicates the environmental condition of the first ID node exceeds theenvironmental threshold condition for the first ID node according to thecontext data for the first ID node; and (d) the environmental conditionvalue indicates the environmental condition of the second ID nodeexceeds the environmental threshold condition for the second ID nodeaccording to the context data for the second ID node.

The environmental anomaly detected in step 2830 of method 2800 may comein a variety of types depending on the type of sensors used as well. Forexample, a further embodiment of step 2830 may have the command nodedetect the environmental anomaly for the shipping container to be a firewithin the shipping container when the temperature value exceeds atemperature threshold maintained by the command node as part of thecontext data for the first ID node and when the barometric pressurevalue exceeds a pressure threshold maintained by the command node aspart of the context data for the second ID node. Another embodiment ofstep 2830 may have the command node detect the environmental anomaly forthe shipping container to be an explosion within the shipping containerwhen the temperature value exceeds a temperature threshold maintained bythe command node as part of the context data for the first ID node andwhen the barometric pressure value is below a pressure thresholdmaintained by the command node as part of the context data for thesecond ID node. Yet another embodiment of step 2830 may have the commandnode detect the environmental anomaly for the shipping container to bean explosion within the shipping container when the temperature valueexceeds a temperature threshold maintained by the command node as partof the context data for the first ID node and when the barometricpressure value drops faster than a pressure drop threshold maintained bythe command node as part of the context data for the second ID node. Afurther embodiment of step 2830 may have the command node detect theenvironmental anomaly for the shipping container to be a detectedchemical related fire within the shipping container when the temperaturevalue exceeds a temperature threshold maintained by the command node aspart of the context data for the first ID node and when the detectedchemical matches a predetermined chemical profile maintained by thecommand node as part of the context data for the second ID node. Andstill another embodiment of step 2830 may have the command node detectthe environmental anomaly for the shipping container to be a radiationleak within the shipping container when the temperature value exceeds atemperature threshold maintained by the command node as part of thecontext data for the first ID node and when the detected radiationmatches a predetermined radiation profile maintained by the command nodeas part of the context data for the second ID node.

In other embodiments, method 2800 may detect the environmental anomalybased upon relative changes in sensor data when compared to the relevantcontext data on environmental threshold conditions. For example, steps2825 and 2830 may have the command node detecting an environmentalanomaly when the comparison of the detected sensor data and the contextdata in step 2820 indicates a relative change in the environmentalcondition for at least one of the ID nodes and where such a relativechange exceeds its respective environmental threshold condition (whichmay be defined in terms of relative changes in environmental conditions,such as temperature, pressure, and the like). In a more detailedexample, step 2830 may further have the command node comparing arelative change in the detected sensor data from at least one of the IDnodes and the locally maintained context data for that one of the IDnodes, which has the environmental threshold condition for at least thatID node as a threshold relative environmental change condition that whenexceeded is indicative of the environmental anomaly for the shippingcontainer. As such in this example, detecting the environmental anomalyfor the shipping container in this embodiment of step 2830 occurs whenthe comparison of the detected sensor data and the context dataindicates the environmental condition for that ID node exceeds thethreshold relative environmental change condition.

At step 2835, method 2800 proceeds with the command node generating alayered alert notification related to the environmental anomaly for theshipping container in response to detecting the environmental anomaly.The layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority based upon the comparison of the receivedsensor data and the context data. In a further embodiment of method2800, the targeted mediation recipient may be automatically selected bythe command node based upon an excess condition on how much the detectedsensor data and the context data indicates the environmental conditionfor at least one of the ID nodes exceeds the environmental thresholdcondition for that ID node. Such a targeted mediation recipientidentified by the command node in the layered alert notification may be,for example, a triggered fire suppression system on the transit vehicle(e.g., exemplary fire suppression system 25010 of FIG. 25B) that isoperative to automatically respond to the detected environmental anomalybased upon receipt of the layered alert notification; an operator of thetransit vehicle that can alter movement of the transit vehicle; or alogistics crew member of the transit vehicle that can inspect theshipping container.

In another further embodiment of method 2800, the targeted mediationaction identified by the command node in step 2835 may be automaticallyselected by the command node based upon an excess condition on how muchthe detected sensor data and the context data indicates theenvironmental condition for at least one of the ID nodes exceeds theenvironmental threshold condition for that ID node. In more detail, thetargeted mediation action identified by the command node in the layeredalert notification may depend upon what is loaded within the shippingcontainer as indicated by shipping information maintained on the commandnode or may depend upon an excess condition on how many of the ID nodeshave their detected sensor data and their context data indicating thattheir environmental condition exceed the environmental thresholdcondition for the ID nodes. With such information, the command node mayidentify an appropriate targeted mediation action, such as immediatelydeploying the onboard fire suppression system or, instead, identify athreat appropriate action of notifying logistics personnel to inspectthe shipping container.

The targeted mediation action in step 2835 may be identified by thecommand node using a variety of types of context data so that thetargeted mediation action may be automatically identified with an robustand improved sense of contextual understanding of the situation. Forexample, in a further embodiment, method 2800 may have the command nodereceiving vehicle status data from the external transceiver unitassociated with the transit vehicle, so that the targeted mediationaction identified by the command node in the layered alert notificationmay depend upon a state of the transit vehicle as indicated by thevehicle status data. Such a state of the transit vehicle may include,for example, a takeoff vehicular status, a cruising vehicular status, alanding vehicular status, and an on-the-ground vehicular status. Thus,context data 26560 may include such vehicle status data, which may beused in identifying the targeted mediation action in response todetecting the environmental anomaly.

In another example, an embodiment of method 2800 may have the commandnode accessing container status data maintained by the command node andassociated with the shipping container, so that the targeted mediationaction identified by the command node in the layered alert notificationdepends upon a state of the shipping container as indicated in thecontainer status data. In yet another example, an embodiment of method2800 may have the command node detecting geolocation data related to acurrent location of the shipping container within the transit vehicle,so that the targeted mediation action identified by the command node inthe layered alert notification depends upon the current location of theshipping container as indicated in the geolocation data. In stillanother example, an embodiment of method 2800 may have the command nodeaccessing loading plan data maintained by the command node (where suchloading plan data indicates a relative location of the shippingcontainer within the transit vehicle), so that the targeted mediationaction identified by the command node in the layered alert notificationdepends upon the relative location of the shipping container within thetransit vehicle as indicated in the loading plan data. And in anotherexample, an embodiment of method 2800 may have the command nodeaccessing facility status data maintained by the command node andassociated with a storage facility for the shipping container, so thatthe targeted mediation action identified by the command node in thelayered alert notification depends upon a state of the storage facilityas indicated in the facility status data.

The targeted mediation response identified in step 2835 may also takeseveral forms. For example, a further embodiment may have the targetedmediation response identified by the command node in the layered alertnotification be an automatic response by a triggered fire suppressionsystem on the transit vehicle; a request to change course of the transitvehicle from an existing travel path of the transit vehicle; or arequest to investigate the shipping container.

Likewise, the mediation response priority established by the commandnode as part of step 2835 may take several forms. For example, thecommand node may establish the mediation response priority as part ofstep 2835 by automatically selecting the mediation response prioritybased upon an excess condition on how much the detected sensor data andthe context data indicates the environmental condition for at least oneof the ID nodes exceeds the environmental threshold condition for the IDnode(s). In another example, the mediation response priority establishedby the command node as part of the layered alert notification may beestablished as a high priority level indicating further travel by thetransit vehicle is to be at least minimized when responding to thedetected environmental anomaly, or as an intermediate priority levelindicating further travel by the transit vehicle is permissible whenresponding to the detected environmental anomaly.

At step 2840, method 2800 proceeds with the command node transmittingthe layered alert notification to the transceiver unit to initiate amediation response related to the targeted mediation action. In thisway, the command node (e.g., command node 24160 as shown in FIG. 24C)automatically and responsively monitors its particular shippingcontainer by means of the ID nodes disposed and dispersed within theshipping container and responsively provides an enhanced type ofnotification in the form of the layered alert notification to thetransit vehicle's external transceiver (e.g., transceiver 24150 in FIG.24C), which is used to cause the external transceiver to initiate theidentified type of mediation response related to the identified type oftargeted mediation action to deal with the detected environmentalanomaly in a rapid, improved, and more robust manner. Thereafter, method2800 may proceed back to step 2805 where further sensor data may begenerated by each of the ID nodes.

Further embodiments of method 2800 may provide more detailed steps aswell as additional steps. For example, in a more detailed embodiment,the ID nodes generate sensor data over a particular time period and thecommand node, as part of step 2815, may monitor the generated sensordata from each of the ID nodes over the time period to identify relativechanges in the generated sensor data over the time period. Thereafter,as part of step 2820, the step of comparing may have the command nodecomparing the identified relative changes in the generated sensor dataand locally maintained context data (e.g., context data 26560) relatedto those of the ID nodes that are related to the relative changes in thegenerated sensor data. Here, the context data stored on the command nodeincludes at least a plurality of relative environmental thresholdconditions respectively corresponding to the different ID nodes.Further, as part of steps 2825 and 2830, the step of detecting theenvironmental anomaly for the shipping container may occur when thecomparison of identified relative changes in the generated sensor dataand locally maintained context data related to those of the ID nodesthat correspond to each of the identified relative changes in thegenerated sensor data indicates a changed environmental condition for atleast one of the ID nodes exceeds its respective relative environmentalthreshold condition. Additionally, as part of step 2835, the commandnode may establish the mediation response priority as being based uponthe comparison of the identified relative changes in the generatedsensor data and the locally maintained context data related to those ofthe ID nodes that correspond to the relative changes in the generatedsensor data.

Another more detailed embodiment of method 2800 may involvesetting/adjusting the rate an ID node generates and broadcasts sensordata as a way to adaptively respond to an initially detectedenvironmental anomaly. For example, step 2810 of broadcasting thegenerated sensor data by the ID nodes may have each of the ID nodestransmitting their respectively generated sensor data according to abroadcast profile maintained by each of the ID nodes, where such abroadcast profile defines a first messaging rate used to regulate howoften the generated sensor data is transmitted to the command node, andwhere the first messaging rate is higher than a default messaging rate.This further embodiment of method 2800 may also have the command nodeinstructing each of the ID nodes to broadcast future generated sensordata at a second messaging rate that exceeds the first messaging rateafter transmitting the layered alert notification to the transceiverunit in step 2840. The first messaging rate for the ID nodes may be setwith an initial value correlated to an environmental risk associatedwith a package within the shipping container, and may adaptively set thesecond messaging rate for the ID nodes to a predetermined messaging ratebased upon a type of material existing within at least one of thepackages within the shipping container. This further embodiment ofmethod 2700 may also have the command node instructing each of the IDnodes to change from the default messaging rate to the first messagingrate. In this way, the command node may adaptively change the messagingrates by which the ID nodes broadcast their sensor data depending on thedetected environmental anomaly and depending on context data (e.g.,context data 26560) about the makeup of what is being transported withinthe shipping container.

Still another embodiment of method 2800 may involve selectively andadaptively choosing which of the ID nodes available within the shippingcontainer to use when monitoring for an environmental anomaly. Forexample, this further embodiment of method 2800 may have the commandnode select each of the ID nodes used for detecting the environmentalanomaly from a larger group of network elements being loaded into theshipping container. In this way, the ID nodes that are selected arethose chosen by the command node to provide the gathered sensor data foruse in detecting the environmental anomaly for the shipping container.In more detail, the ID nodes selected may be identified for selection bythe command node based upon a loading scheme for the shipping container(where such a loading scheme may be maintained in memory of the commandnode as loading plan data that may be stored as part of context data26560).

Yet another embodiment of method 2800 may involve remote altering andupdating of thresholds and mediation information used for detecting anenvironmental anomaly and how to respond to such an environmentalanomaly. For example, this additional embodiment of method 2800 may havethe command node receiving an update for the environmental thresholdconditions for at least one of the ID nodes. Such an update may bereceived from the external transceiver unit (e.g., transceiver 24150 asshown in FIG. 24C). This update received from the external transceivermay be defined by personnel on the transit vehicle (e.g., an operator orlogistics personnel on the transit vehicle using the particular externaltransceiver unit (such as cockpit transceiver 25150 a or logisticstransceiver 25150 b)). Alternatively, the update may be received from aremote control center (e.g., remote control center server 24100 incommunication with external transceiver 24150).

In still a further embodiment of method 2800, the validity ofcommunications (e.g., broadcasted sensor data) may be confirmed orverified to provide a more secure and robust system that is lesssusceptible to error or spoofing by other nodes. In such a furtherembodiment of method 2800, the command node may detect the sensor datain step 2815 by (a) receiving the sensor data broadcasted from a firstof the ID nodes; (b) confirming the validity of the received sensordata; (c) repeat steps (a) and (b) for the remainder of the sensor datareceived from any of the remaining ones of the ID nodes; and (d)compiling the detected sensor data using only the received sensor dataconfirmed valid in sub step (b) of modified step 2815. In more detail,the command node may confirm as part of (b) that it uses only validsensor data when detecting an environmental anomaly in an active orpassive manner. For example, confirming the validity of the receivedsensor data may have the command node actively sending an authenticationrequest to the first of the ID nodes, and receiving a validationresponse back from that ID node that authenticates the sensor databroadcasted from that ID node. In another example, confirming thevalidity of the received sensor data as part of (b) may have the commandnode, in a more passive sense accessing a validation sequence for an IDnode as maintained by the command node in memory (e.g., as part ofsecurity data 435 or profile data 430 on command node 26000 for thatparticular ID node). Such a validation sequence characterizes expectedbroadcasts from that particular ID node. Using such a validationsequence, the command node may then passively determine if the receivedsensor data from that ID node matches a predetermined one of theexpected broadcasts from that ID node without the need to poll orinteractively request authentication from that ID node. Such apredetermined one of the expected broadcasts according to the validationsequence may be a rotating value previously received by the command nodefor that ID node as a way of enhancing security for the command node tobetter determine and confirm that ID node sensor data is coming from avalid ID node and, thus, is valid sensor data upon which to makedeterminations of whether an environmental anomaly exists.

Those skilled in the art will appreciate that method 2800 as disclosedand explained above in various embodiments may be implemented using anexemplary improved monitoring system for detecting an environmentalanomaly in a shipping container that maintains multiple packages and forreporting a layered alert notification related to the environmentalanomaly to an external transceiver unit associated with a transitvehicle transporting the shipping container such as that explained abovewith reference to FIG. 24C and its exemplary elements. Such anembodiment of an improved monitoring system, as explained above relativeto operations according to method 2800 and with elements from FIG. 24C,uses at least multiple ID nodes disposed within the shipping container(e.g., ID nodes 24120 a-24120 f) running one or more ID node monitoringprogram code as part of node control and management code 325 to controloperations of the ID nodes to generate and broadcast sensor data, aswell as a command node mounted to the shipping container (e.g., commandnode 24160 in FIG. 24C) running one or more parts of CN control &management code 26425 to control the operations of the command node aspart of monitoring for and detecting an environmental anomaly using theID node generated sensor data as well as generating the layered alertnotification and transmitting that notification to the externaltransceiver unit to initiate a type of mediation response. Such code maybe stored on a non-transitory computer-readable medium, such as memorystorage 26415 on command node 24160 (an embodiment of exemplary commandnode 26000) and memory storage 315 on ID nodes 24120 a-24120 f(embodiments of exemplary ID node 120 a). Thus, when executing suchcode, the ID nodes and the command node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 2800 and variations of that method.

While exemplary method 2800 and the exemplary system described relativeto FIG. 24C uses ID node generated sensor data (also referred to as IDnode sensor data) where the ID nodes are not required to be associatedwith particular packages within the shipping container and where theenvironmental threshold conditions are related to particular ID nodes,further embodiments may extend this method and system by involvingcommand node sensor data as well. As explained above, an exemplarycommand node (e.g., command node 26000 of FIG. 26) may be implementedand deployed with its own onboard sensor or sensors (e.g., sensors26465). Thus, such additional method and system embodiments may besimilar to what is described above relative to FIGS. 24A and 24C wherespecific packages are shown, but the ID node sensor data and relevantenvironmental threshold conditions focus on particular ID nodes withoutbeing tied to specific packages maintained within shipping container24300, but can also involve sensor data generated by the command node toimprove and enhance how an environmental anomaly related to the shippingcontainer may be detected and how a mediation response may be initiatedvia a layered alert notification to an external transceiver associatedwith a transit vehicle (such as an aircraft, railway conveyance, amaritime vessel, or a roadway conveyance).

FIG. 29 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network using ID node sensor data from ID nodes that aredisposed within the shipping container but are generally not associatedwith particular packages and with environmental threshold conditions forthe ID nodes as well as command node sensor data from a command nodemounted to the shipping container in accordance with an embodiment ofthe invention. In more detail and referring now to FIG. 29, exemplarymethod 2900 describes an improved method for monitoring a shippingcontainer (e.g., ULD shipping container 24300 as shown, for example inFIG. 24C) for an environmental anomaly using a wireless node networkhaving at least a plurality of ID nodes (e.g., ID nodes 24120 a-24120 fshown in FIG. 24C) disposed within the shipping container and a commandnode (e.g., command node 24160 of FIG. 24C) mounted to a predeterminedlocation on the shipping container, where the shipping containermaintains a plurality of packages (e.g., packages 24400 a-24400 c ofFIG. 24C), where each of the ID nodes has at least one ID nodeenvironmental sensor, where the command node has at least one commandnode environmental sensor (e.g., sensor 26465 shown in FIG. 26), andwhere the command node is operative to communicate with each of the IDnodes and an external transceiver unit (e.g., external transceiver 24150of FIG. 24C) associated with a transit vehicle (e.g., transit vehicle24200, which may, for example, be an aircraft, railway conveyance, amaritime vessel, or a roadway conveyance). In general, exemplary method2900 is similar to method 2800 as described above with the addition ofstep 2905 (related to generating command node sensor data by the commandnode) and variations to step 2835 that consider the generated commandnode sensor data part of detecting the environmental anomaly anddetermining what goes into the relevant layered alert notification tothe external transceiver so as to initiate an appropriate mediationresponse to the environmental anomaly.

In more detail, exemplary method 2900 begins at step 2902 withgenerating current sensor data (also referred to current command nodesensor data) using the command node's sensor(s) related to a currentenvironment condition proximate the command node. For example, step 2902may have exemplary command node 24160 (as shown in FIG. 24C) generatingsensor data using one or more of sensor(s) 26465 (similar to sensor 360as explained above). Such exemplary command node sensor data may begenerated, for example, using a single element sensor, multiple sensorelements, or an array of sensor elements that may be of the same type orof different types of environmental sensors onboard the command node. Anembodiment may have such a sensor or sensors operatively coupled to thecommand node's processor 26400, but may be disposed within a housing ofthe command node or may be deployed external to the housing while stillsensing an environmental condition proximate the command node. In thismanner, exemplary current command node sensor data may include a singletype of sensor information or multiple types of sensor informationrelated to a variety of environmental conditions (e.g., pressure,movement, light, temperature, humidity, chemical, radiation, magneticfield, altitude, attitude, orientation, acceleration, and the like).Further embodiment may deploy such command node sensor(s), as part ofthe command node operating as part of step 2902, remotely in differentparts of the shipping container (e.g., along wall surfaces, the ceiling,and/or the base of the shipping container).

At step 2905, the environmental sensor or sensors on each of the IDnodes generate sensor data (also referred to as ID node sensor data)related to an environmental condition proximate the respective ID nodeas disposed within the shipping container. In more detailed embodiment,the environmental sensor for a first of the ID nodes may be atemperature sensor while the environmental sensor for a second of the IDnodes may be a barometric pressure sensor. In another embodiment, theenvironmental sensor for a first of the ID nodes may be a temperaturesensor while the environmental sensor for a second of the ID nodes maybe one from a group consisting of a barometric pressure sensor, aradiation sensor, and a chemical sensor. In still a further embodiment,the environmental sensor for one or more of the ID nodes may havemultiple sensor elements, where such sensor elements may include atleast a temperature sensor element and a barometric pressure sensorelement (but may also include a radiation sensor and/or a chemicalsensor).

In still another further embodiment of method 2900, the ID nodesgenerating ID node sensor data in step 2905 may be in two differentgroups—one of which ID nodes that are disposed on the shipping containeritself and a second group of the ID nodes are associated with differentones of a plurality of packages disposed within the shipping container.Further still, the ID nodes generating sensor data in step 2905 may bein a third group—namely, ID nodes that are disposed within the shippingcontainer but not affixed to the shipping container itself

At step 2910, method 2900 proceeds with each of the ID nodesbroadcasting their respectively generated sensor data about theenvironmental condition proximate the particular ID node within theshipping container. At step 2915, method 2800 has the command nodedetecting the sensor data broadcasted from the ID nodes. Method 2900then proceeds to step 2920 where the command node compares the detectedsensor data from each of the ID nodes and locally maintained contextdata related to each of the ID nodes. Such context data (e.g., contextdata 26560) includes at least a plurality of environmental thresholdconditions respectively corresponding to the different ID nodes. In moredetail, the environmental threshold condition for each of the ID nodesmay depend on where a particular ID node is located within the shippingcontainer or what is placed next to each of the ID nodes according to aloading scheme for the shipping container maintained in memory of thecommand node as loading plan data. In another example, the environmentalthreshold condition for each of the ID nodes as indicated by the contextdata may be a dynamic value that changes or is updated (as discussedherein) when what is placed next to each of the ID nodes within theshipping container changes. In this manner, a command node for theshipping container may have the environmental threshold conditions forthe ID nodes within the shipping container being updated, changed, andrevised as the contents of the shipping container changes and as what isin the container is moved or relocated within the shipping container.

At decision step 2925, method 2900 has the command node determining ifan environmental condition for one of the ID nodes exceeds itsrespective environmental threshold condition based upon the comparisonperformed in step 2920. If so, method 2900 proceeds from step 2925directly to step 2930 where the command node detects the environmentalanomaly. If not, method 2900 proceeds from step 2925 back to step 2902where the command node generates more command node sensor data and thento step 2905 where the ID nodes generate more ID node sensor data andthe ID nodes continue to broadcast newly generated sensor data at step2910 for detection and consideration by the command node in steps2915-2925 again.

In steps 2925-2930, the command node may detect different types ofenvironmental anomalies depending on the type of environmental sensordata being considered as generated and broadcast from the ID nodes. Forexample, a further embodiment of method 2900 may have the command nodedetecting the environmental anomaly as part of steps 2925-2930 when (a)the sensor data detected from one of the ID nodes comprises atemperature value; (b) the sensor data detected from a second of the IDnodes comprises a barometric pressure value; (c) the temperature valueindicates the environmental condition of the first ID node exceeds theenvironmental threshold condition for the first ID node according to thecontext data for the first ID node; and (d) the barometric pressurevalue indicates the environmental condition of the second ID nodeexceeds the environmental threshold condition for the second ID nodeaccording to the context data for the second ID node.

Still further embodiments of method 2900 may use a combination oftemperature and other types of ID node sensors. For example, anotherembodiment of method 2900 may have the command node detecting theenvironmental anomaly as part of steps 2925-2930 when (a) the sensordata detected from one of the ID nodes comprises a temperature value;(b) the sensor data detected from a second of the ID nodes comprises anenvironmental condition value of one of a sensed barometric pressurelevel by the barometric sensor, a detected radiation level by theradiation sensor, or a detected chemical by the chemical sensor (e.g.,the detected chemical by the chemical sensor may be indicative of anexplosive, a fire, or the presence of either CO or CO₂); (c) thetemperature value indicates the environmental condition of the first IDnode exceeds the environmental threshold condition for the first ID nodeaccording to the context data for the first ID node; and (d) theenvironmental condition value indicates the environmental condition ofthe second ID node exceeds the environmental threshold condition for thesecond ID node according to the context data for the second ID node.

The environmental anomaly detected in step 2930 of method 2900 may comein a variety of types depending on the type of ID node sensors used aswell. For example, a further embodiment of step 2930 may have thecommand node detect the environmental anomaly for the shipping containerto be a fire within the shipping container when the temperature valueexceeds a temperature threshold maintained by the command node as partof the context data for the first ID node and when the barometricpressure value exceeds a pressure threshold maintained by the commandnode as part of the context data for the second ID node. Anotherembodiment of step 2930 may have the command node detect theenvironmental anomaly for the shipping container to be an explosionwithin the shipping container when the temperature value exceeds atemperature threshold maintained by the command node as part of thecontext data for the first ID node and when the barometric pressurevalue is below a pressure threshold maintained by the command node aspart of the context data for the second ID node. Yet another embodimentof step 2930 may have the command node detect the environmental anomalyfor the shipping container to be an explosion within the shippingcontainer when the temperature value exceeds a temperature thresholdmaintained by the command node as part of the context data for the firstID node and when the barometric pressure value drops faster than apressure drop threshold maintained by the command node as part of thecontext data for the second ID node. A further embodiment of step 2930may have the command node detect the environmental anomaly for theshipping container to be a detected chemical related fire within theshipping container when the temperature value exceeds a temperaturethreshold maintained by the command node as part of the context data forthe first ID node and when the detected chemical matches a predeterminedchemical profile maintained by the command node as part of the contextdata for the second ID node. And still another embodiment of step 2930may have the command node detect the environmental anomaly for theshipping container to be a radiation leak within the shipping containerwhen the temperature value exceeds a temperature threshold maintained bythe command node as part of the context data for the first ID node andwhen the detected radiation matches a predetermined radiation profilemaintained by the command node as part of the context data for thesecond ID node.

In other embodiments, method 2900 may detect the environmental anomalybased upon relative changes in ID node sensor data when compared to therelevant context data on environmental threshold conditions. Forexample, steps 2925 and 2930 may have the command node detecting anenvironmental anomaly when the comparison of the detected ID node sensordata and the context data in step 2920 indicates a relative change inthe environmental condition over a time period for at least one of theID nodes and where such a relative change exceeds its respectiveenvironmental threshold condition (which may be defined in terms ofrelative changes in environmental conditions, such as temperature,pressure, and the like). In other words, the relative change in theenvironmental condition may be compared to a predefined thresholddifference (e.g., a predefined relative temperature change over the timeperiod). In a more detailed example, step 2930 may further have thecommand node comparing a relative change in the detected ID node sensordata from at least one of the ID nodes and the locally maintainedcontext data for that one of the ID nodes, which has the environmentalthreshold condition for at least that ID node as a threshold relativeenvironmental change condition that when exceeded is indicative of theenvironmental anomaly for the shipping container. As such in thisexample, detecting the environmental anomaly for the shipping containerin this embodiment of step 2930 occurs when the comparison of thedetected ID node sensor data and the context data indicates theenvironmental condition for that ID node exceeds the threshold relativeenvironmental change condition.

In a further embodiment of method 2900, step 2930 may have the commandnode detecting the environmental anomaly when at least one of (a) thecomparison of the detected ID node sensor data and the context data instep 2920 indicates an environmental condition proximate at least one ofthe ID nodes exceeds its respective environmental threshold condition,and (b) the difference between the current command node sensor data anda shipping container environmental profile exceeds a shipping containerthreshold condition. Thus, in this further embodiment, the process ofdetecting the environmental anomaly (and not just how to respond to thedetected environmental anomaly) may be enhanced by considering currentcommand node sensor data relative to the shipping container'senvironmental profile (e.g., maintained as part of profile data 430 onthe command node) and a particular shipping container level thresholdcondition (e.g., maintained as part of context data 26560). In moredetail, method 2900 may also include having the command nodeenvironmental sensor capturing shipping container characterizationsensor data over a characterization time period, so that the shippingcontainer characterization sensor data is related to an environmentcondition proximate the predetermined location on the shipping containerover the characterization time period and storing the shipping containerenvironmental profile (e.g., part of profile data 430) based on theshipping container characterization sensor data.

At step 2935, method 2900 proceeds with the command node generating alayered alert notification related to the environmental anomaly for theshipping container in response to detecting the environmental anomaly.In step 2935, exemplary method 2900 has the command node generating thelayered alert notification as identifying a targeted mediationrecipient, identifying a targeted mediation action, and establishing amediation response priority based upon (a) the comparison of thereceived ID node sensor data and the context data from step 2920, and(b) a difference between the current command node sensor data and ashipping container environmental profile maintained by the command node(e.g., part of profile data 430 maintained on command node 26000).

In a further embodiment of method 2900, the targeted mediation recipientmay be automatically selected by the command node based upon an excesscondition on how much the detected ID node sensor data and the contextdata indicates the environmental condition for at least one of the IDnodes exceeds the environmental threshold condition for that ID node.Such a targeted mediation recipient identified by the command node inthe layered alert notification may be, for example, a triggered firesuppression system on the transit vehicle (e.g., exemplary firesuppression system 25010 of FIG. 25B) that is operative to automaticallyrespond to the detected environmental anomaly based upon receipt of thelayered alert notification; an operator of the transit vehicle that canalter movement of the transit vehicle; or a logistics crew member of thetransit vehicle that can inspect the shipping container.

In another further embodiment of method 2900, the targeted mediationaction identified by the command node in step 2935 may be automaticallyselected by the command node based upon an excess condition on how muchthe detected ID node sensor data and the context data indicates theenvironmental condition for at least one of the ID nodes exceeds theenvironmental threshold condition for that ID node. In more detail, thetargeted mediation action identified by the command node in the layeredalert notification may depend upon what is loaded within the shippingcontainer as indicated by shipping information maintained on the commandnode or may depend upon an excess condition on how many of the ID nodeshave their detected sensor data and their context data indicating thattheir environmental condition exceed the environmental thresholdcondition for the ID nodes. With such information, the command node mayidentify an appropriate targeted mediation action, such as immediatelydeploying the onboard fire suppression system or, instead, identify athreat appropriate action of notifying logistics personnel to inspectthe shipping container.

The targeted mediation action in step 2935 may be identified by thecommand node using a variety of types of context data so that thetargeted mediation action may be automatically identified with an robustand improved sense of contextual understanding of the situation. Forexample, in a further embodiment, method 2900 may have the command nodereceiving vehicle status data from the external transceiver unitassociated with the transit vehicle, so that the targeted mediationaction identified by the command node in the layered alert notificationmay depend upon a state of the transit vehicle as indicated by thevehicle status data. Such a state of the transit vehicle may include,for example, a takeoff vehicular status, a cruising vehicular status, alanding vehicular status, and an on-the-ground vehicular status. Thus,context data 26560 may include such vehicle status data, which may beused in identifying the targeted mediation action in response todetecting the environmental anomaly.

In another example, an embodiment of method 2900 may have the commandnode accessing container status data maintained by the command node andassociated with the shipping container, so that the targeted mediationaction identified by the command node in the layered alert notificationdepends upon a state of the shipping container as indicated in thecontainer status data. In yet another example, an embodiment of method2900 may have the command node detecting geolocation data related to acurrent location of the shipping container within the transit vehicle,so that the targeted mediation action identified by the command node inthe layered alert notification depends upon the current location of theshipping container as indicated in the geolocation data. In stillanother example, an embodiment of method 2900 may have the command nodeaccessing loading plan data maintained by the command node (where suchloading plan data indicates a relative location of the shippingcontainer within the transit vehicle), so that the targeted mediationaction identified by the command node in the layered alert notificationdepends upon the relative location of the shipping container within thetransit vehicle as indicated in the loading plan data. And in anotherexample, an embodiment of method 2900 may have the command nodeaccessing facility status data maintained by the command node andassociated with a storage facility for the shipping container, so thatthe targeted mediation action identified by the command node in thelayered alert notification depends upon a state of the storage facilityas indicated in the facility status data.

The targeted mediation response identified in step 2935 may also takeseveral forms. For example, a further embodiment may have the targetedmediation response identified by the command node in the layered alertnotification be an automatic response by a triggered fire suppressionsystem on the transit vehicle; a request to change course of the transitvehicle from an existing travel path of the transit vehicle; or arequest to investigate the shipping container.

Likewise, the mediation response priority established by the commandnode as part of step 2935 may take several forms. For example, thecommand node may establish the mediation response priority as part ofstep 2935 by automatically selecting the mediation response prioritybased upon an excess condition on how much the detected ID sensor dataand the context data indicates the environmental condition for at leastone of the ID nodes exceeds the environmental threshold condition forthe ID node(s). In another example, the mediation response priorityestablished by the command node as part of the layered alertnotification may be established as a high priority level indicatingfurther travel by the transit vehicle is to be at least minimized whenresponding to the detected environmental anomaly, or as an intermediatepriority level indicating further travel by the transit vehicle ispermissible when responding to the detected environmental anomaly.

At step 2940, method 2900 proceeds with the command node transmittingthe layered alert notification to the external transceiver unit toinitiate a mediation response related to the targeted mediation action.Thereafter, method 2900 may proceed back to steps 2902 and 2905 wherefurther sensor data may be generated by the command node and each of theID nodes.

Further embodiments of method 2900 may provide more detailed steps aswell as additional steps. For example, in a more detailed embodiment,the ID nodes generate ID node sensor data over a particular time periodand the command node, as part of step 2915, may monitor the generated IDnode sensor data from each of the ID nodes over the time period toidentify relative changes in the generated ID node sensor data over thetime period. Thereafter, as part of step 2920, the step of comparing mayhave the command node comparing the identified relative changes in thegenerated ID node sensor data and locally maintained context data (e.g.,context data 26560) related to those of the ID nodes that are related tothe relative changes in the generated ID node sensor data. Here, thecontext data stored on the command node includes at least a plurality ofrelative environmental threshold conditions respectively correspondingto the different ID nodes. Further, as part of steps 2925 and 2930, thestep of detecting the environmental anomaly for the shipping containermay occur when the comparison of identified relative changes in thegenerated ID sensor data and locally maintained context data related tothose of the ID nodes that correspond to each of the identified relativechanges in the generated ID node sensor data indicates a changedenvironmental condition for at least one of the ID nodes exceeds itsrespective relative environmental threshold condition. Furthermore,generating the layered alert notification in step 2935 may have thecommand node identifying a targeted mediation recipient, identifying atargeted mediation action, and establishing a mediation responsepriority based upon (a) the comparison of the relative changes in the IDnode sensor data to the context data and (b) a difference betweenrelative changes in command node sensor data and a shipping containerenvironmental profile maintained by the command node. In more detail aspart of step 2935, the command node may establish the mediation responsepriority as being based upon (c) a relative change between the currentcommand node sensor data related to the current environmental conditionproximate the command node and a prior value for the current commandnode sensor data related to a prior environmental condition proximatethe command node.

Another more detailed embodiment of method 2900 may involvesetting/adjusting the rate an ID node generates and broadcasts ID nodesensor data as a way to adaptively respond to an initially detectedenvironmental anomaly. For example, step 2910 of broadcasting thegenerated ID node sensor data by the ID nodes may have each of the IDnodes transmitting their respectively generated ID node sensor dataaccording to a broadcast profile maintained by each of the ID nodes,where such a broadcast profile defines a first messaging rate used toregulate how often the generated ID node sensor data is transmitted tothe command node, and where the first messaging rate is higher than adefault messaging rate. This further embodiment of method 2900 may alsohave the command node instructing each of the ID nodes to broadcastfuture generated ID node sensor data at a second messaging rate thatexceeds the first messaging rate after transmitting the layered alertnotification to the transceiver unit in step 2940. The first messagingrate for the ID nodes may be set with an initial value correlated to anenvironmental risk associated with a package within the shippingcontainer, and may adaptively set the second messaging rate for the IDnodes to a predetermined messaging rate based upon a type of materialexisting within at least one of the packages within the shippingcontainer. This further embodiment of method 2700 may also have thecommand node instructing each of the ID nodes to change from the defaultmessaging rate to the first messaging rate. In this way, the commandnode may adaptively change the messaging rates by which the ID nodesbroadcast their ID node sensor data depending on the detectedenvironmental anomaly and, in some embodiments, depending on contextdata (e.g., context data 26560) about the makeup of what is beingtransported within the shipping container.

Still another embodiment of method 2900 may involve selectively andadaptively choosing which of the ID nodes available within the shippingcontainer to use when monitoring for an environmental anomaly. Forexample, this further embodiment of method 2900 may have the commandnode select each of the ID nodes used for detecting the environmentalanomaly from a larger group of network elements being loaded into theshipping container. In this way, the ID nodes that are selected arethose specifically identified or chosen by the command node to providethe gathered ID node sensor data for use in detecting the environmentalanomaly for the shipping container. In more detail, the ID nodesselected may be identified for selection by the command node based upona loading scheme for the shipping container (where such a loading schememay be maintained in memory of the command node as loading plan datathat may be stored as part of context data 26560).

Yet another embodiment of method 2900 may involve remote altering andupdating of thresholds and mediation information used for detecting anenvironmental anomaly and how to respond to such an environmentalanomaly. For example, this additional embodiment of method 2900 may havethe command node receiving an update for the environmental thresholdconditions for at least one of the ID nodes. Such an update may bereceived from the external transceiver unit (e.g., transceiver 24150 asshown in FIG. 24C). This update received from the external transceivermay be defined by personnel on the transit vehicle (e.g., an operator orlogistics personnel on the transit vehicle using the particular externaltransceiver unit (such as cockpit transceiver 25150 a or logisticstransceiver 25150 b) and its user input interface(s)). Alternatively,the update may be received from a remote control center (e.g., remotecontrol center server 24100 in communication with external transceiver24150).

In still a further embodiment of method 2900, the validity ofcommunications from ID nodes (e.g., broadcasted ID node sensor data) maybe confirmed or verified to provide a more secure and robust system andmethod of operation that is less susceptible to error or spoofing byother nodes. In such a further embodiment of method 2900, the commandnode may detect the ID node sensor data in step 2915 by (a) receivingthe ID node sensor data broadcasted from a first of the ID nodes; (b)confirming the validity of the received ID node sensor data; (c) repeatsteps (a) and (b) for the remainder of the ID node sensor data receivedfrom any of the remaining ones of the ID nodes; and (d) compiling thedetected ID node sensor data using only the received ID node sensor dataconfirmed valid in sub step (b) of modified step 2915. In more detail,the command node may confirm as part of (b) that it uses only valid IDnode sensor data when detecting an environmental anomaly in an active orpassive manner. For example, confirming the validity of the received IDnode sensor data may have the command node actively sending anauthentication request to the first of the ID nodes, and receiving avalidation response back from that ID node that authenticates the IDnode sensor data broadcasted from that ID node. In another example,confirming the validity of the received ID node sensor data as part of(b) may have the command node, in a more passive sense accessing avalidation sequence for an ID node as maintained by the command node inmemory (e.g., as part of security data 435 or profile data 430 oncommand node 26000 for that particular ID node). Such a validationsequence characterizes expected broadcasts from that particular ID node.Using such a validation sequence, the command node may then passivelydetermine if the received ID node sensor data from that ID node matchesa predetermined one of the expected broadcasts from that ID node withoutthe need to poll or interactively request authentication from that IDnode. Such a predetermined one of the expected broadcasts according tothe validation sequence may be, for example, a rotating value previouslyreceived by the command node for that ID node as a way of enhancingsecurity for the command node to better determine and confirm that IDnode sensor data is coming from a valid ID node and, thus, is valid IDnode sensor data upon which to make determinations of whether anenvironmental anomaly exists.

Those skilled in the art will appreciate that method 2900 as disclosedand explained above in various embodiments may be implemented using anexemplary improved monitoring system for detecting an environmentalanomaly in a shipping container that maintains multiple packages and forreporting a layered alert notification related to the environmentalanomaly to an external transceiver unit associated with a transitvehicle transporting the shipping container such as that explained abovewith reference to FIG. 24C and its exemplary elements. Such anembodiment of this exemplary improved monitoring system, as explainedabove relative to operations according to method 2900 and with elementsfrom FIG. 24C, may use at least multiple ID nodes disposed within theshipping container (e.g., ID nodes 24120 a-24120 f) running one or moreID node monitoring program code as part of node control and managementcode 325 to control operations of the ID nodes to generate and broadcastID node sensor data, as well as a command node mounted to the shippingcontainer (e.g., command node 24160 in FIG. 24C) having a command nodeenvironmental sensor (e.g., sensor(s) 26465) running one or more partsof CN control & management code 26425 to control the operations of thecommand node as part of monitoring for and detecting an environmentalanomaly using the ID node generated sensor data as well as generatingthe layered alert notification and transmitting that notification to theexternal transceiver unit to initiate a type of mediation response. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 26415 on command node 24160 (an embodiment of exemplarycommand node 26000) and memory storage 315 on ID nodes 24120 a-24120 f(embodiments of exemplary ID node 120 a). Thus, when executing suchcode, the ID nodes and the command node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 2900 and variations of that method.

In yet another more detailed system embodiment, a further improvedsystem is described for detecting and automatically reporting on anenvironmental anomaly in a shipping container onboard a transit vehiclewhere the shipping container maintains multiple packages. In general, anembodiment of this improved system is illustrated in FIG. 24A or 24B.Such an embodiment includes at least multiple ID sensor nodes disposedwithin the shipping container (e.g., ID nodes 24120 a-24120 c), acommand node mounted to the shipping container (e.g., command node24160), and a transit vehicle transceiver in communication with thecommand node (e.g., external transceiver 24150).

In more detail, the system's ID sensor nodes are disposed within theshipping container (e.g., ULD container 24300), where each of the IDsensor nodes are associated with a respective one of the packages (e.g.,packages 24400 a-2440 c as shown in the system embodiment of FIG. 24A,or packages 24400 d-24400 f as shown in the system embodiment of FIG.24B) maintained within the shipping container. Each of the ID sensornodes have at least an ID sensor node processing unit (commonly referredto as an ID sensor node processor), an ID sensor node memory coupled tothe ID sensor node processing unit, at least one environmental sensor,and a wireless radio transceiver (e.g., a hardware radio, a wirelesstransceiver implemented with a combination of hardware and software, ora software defined radio (SDR) implementation of a wireless radiotransceiver). The ID sensor node's memory is operatively coupled to theID sensor node processing unit and maintains at least an ID sensor nodemonitoring program code (e.g., part of the node control and managementcode 325). The ID sensor node's environmental sensor is configured togenerate sensor data related to an environmental condition of therespective package associated with that particular ID sensor node. Andthe ID sensor node's wireless radio transceiver is operatively coupledto the ID sensor node processing unit, and configured to access thesensor data generated by the environmental sensor and broadcast thesensor data in response to a report command from the ID sensor nodeprocessing unit when the ID sensor node processing unit executes the IDsensor node monitoring program code. The system's command node mountedto the shipping container includes at least a command node processingunit, a command node memory coupled to the command node processing unit,and two communication interfaces each being operatively coupled to thecommand node processing unit. The command node memory maintains at leastcommand node container management program code and context data relatedto each of the ID sensor nodes and including at least environmentalthreshold conditions respectively corresponding to each of the packages.As for the communication interfaces, a first one is configured tocommunicate with each of the ID sensor nodes using a first wirelesscommunication format compatible with the wireless radio transceiver oneach of the ID sensor nodes, while a second one is configured tocommunicate over a second wireless communications format with thesystem's transit vehicle transceiver, which has at least a displayinterface and a fire suppression system interface with which tocommunication with a fire suppression system on the transit vehicle.

In operation, the system's command node processing unit isprogrammatically configured, when executing the command node containermanagement program code, to be operative to detect the sensor databroadcasted from the ID sensor nodes using the first communicationinterface and compare the detected sensor data from each of the IDsensor nodes and the context data related to each of the ID sensornodes. The command node processing unit is also operative to detect theenvironmental anomaly for the shipping container when the comparison ofthe detected sensor data and the context data indicates an environmentalcondition for at least one of the packages exceeds its respectiveenvironmental threshold condition. In response to detecting theenvironmental anomaly, the command node processing unit is operative togenerate a layered alert notification related to the environmentalanomaly for the shipping container where the layered alert notificationidentifies a targeted mediation recipient, identifies a targetedmediation action, and establishes a mediation response priority basedupon the comparison of the received sensor data and the context data.The command node processing unit is then operative to cause the secondcommunication interface to transmit the layered alert notification tothe transit vehicle transceiver to initiate a mediation response relatedto the targeted mediation action.

The system's transit vehicle transceiver, in response to receiving thelayered alert notification, is operative to automatically generate amediation message as the mediation response (where the mediation messagereflects the targeted mediation action and the mediation responsepriority) and provide the mediation message to the targeted mediationrecipient. In a further embodiment, the system's the transit vehicletransceiver may also be operative to automatically generate themediation message as a trigger message for the fire suppression systemon the transit vehicle, and provide the mediation message to the firesuppression system over the fire suppression system interface to causethe fire suppression system to automatically initiate a fire suppressionresponse on the shipping container.

In yet a further embodiment, the system's transit vehicle transceivermay be further operative to automatically generate the mediation messageas a warning message to an operator of the transit vehicle as thetargeted mediation recipient, and provide the warning message to theoperator of the transit vehicle using the display interface of thetransit vehicle transceiver and/or to one or more logistics crew memberof the transit vehicle as the targeted mediation recipient. Such awarning message may, for example, reflect the mediation responsepriority (e.g., an immediate priority requesting a change in directionfor the transit vehicle) or be a prompted request for the logistics crewmember to initiate a responsive action for the shipping container (e.g.,a requested directive to inspect the shipping container or a directiveto trigger the fire suppression system after an inspection of theshipping container).

Unresponsive Node Monitoring for Detecting an Environmental Anomaly

The embodiments described herein address the timely detection of anenvironmental anomaly related to a shipping container, especially withlithium fires within shipping containers aboard vessels/vehicles (e.g.,aircrafts, vehicles, trains, ships, etc.) where damage can spreadquickly and loss of life is more likely if not quickly treated. Theembodiments described thus far above may rely upon sensor data generatedby various nodes as part of detecting an environmental anomaly, butother embodiments may monitor the ability to communicate with such nodes(e.g., ID nodes) instead of monitoring just the sensor data generated bysuch nodes. In more detail, embodiments may monitor for a shift inbehavior of several nodes known to be within a shipping container (notjust monitoring sensor data, such as temperature or pressure data) and,in some embodiments, monitor communications from nodes and sense thesituation of no longer being able to communicate with a threshold numberof the nodes. As explained in more detail below, this may be contextdriven in that the command node may be aware that there is no otherreason for the ID node to leave the container or to shut down and notcommunicate—i.e., the ID node is anticipated to be communicating basedupon a profile or other context data. In other words, embodiments mayhave command node using a communication profile for monitored ID nodesthat indicates when the ID nodes are supposed to broadcast. The ID node,in some cases, may be generally disposed within the shipping containerunassociated with a package, may be traveling within a package, or itmay be affixed to the outside of the package or integrated withinpackaging material of the package. Alert generation may also be layeredbased on, for example, which nodes are changing behavior and where thenodes are within the container.

Referring back to the illustrated example shown in FIG. 24C, anembodiment may have exemplary command node 24160 monitoring exemplary IDnodes 24120 a-24120 f for communications that may be broadcast from eachof those nodes (not necessarily sensor data broadcasts). Some of theseID nodes (e.g., ID nodes 24120 a-24120 c) may be associated withrespective different packages (e.g., packages 24400 a-24400 c), whileanother group of these ID nodes may not be associated with particularpackages and, instead, are disposed in different parts of the shippingcontainer (e.g., ULD container 24300) outside of the packages. Commandnode 24160 may monitor some or all of these ID nodes (depending on theembodiment) for an unanticipated state of ceased broadcasting from anyof the monitored ID nodes according to a communication profilemaintained on the command node 24160 for each the ID nodes (e.g., acommunication profile stored as part of profile data 430 on the commandnode 24160). Based upon this monitoring, command node 24160 may senseand find a group of the monitored ID nodes should be broadcasting buthave stopped broadcasting (i.e., are in an unanticipated state of ceasedbroadcasting). Command node 24160 may detect the environmental anomalywhen a size of this initial group of the monitored but non-communicativeID nodes anticipated to be broadcasting exceeds a threshold settingmaintained by the command node (e.g., as part of context data 26560 orseparately stored as in another data structure in memory of the commandnode), and then responsively generate a layered alert notificationrelated to the detected environmental anomaly for the shippingcontainer. Such a layered alert notification may identify a targetedmediation recipient, identify a targeted mediation action, and establisha mediation response priority based upon a size of the sensed initialgroup of the ID nodes and context data related to the sensed initialgroup of the ID nodes. The command node 24160 may then transmit thelayered alert notification to the transceiver 24150 to initiate amediation response related to the targeted mediation action. Moredetailed exemplary method and system embodiments are described belowthat generally relate to the example elements shown in FIG. 24C asexplained in more detail below.

FIG. 30 is a flow diagram illustrating an exemplary method formonitoring a shipping container (e.g., ULD shipping container 24300) foran environmental anomaly using a wireless node network based uponunanticipated communications from ID nodes (e.g., ID nodes 24120 a-24120f) that are disposed within the shipping container in accordance with anembodiment of the invention. The command node operating as part ofexemplary method 3000 described below may, for example, be implementedas part of the shipping container or separately from the shippingcontainer. Such an exemplary command node (as explained in more detailabove relative to exemplary command node 26000 and command node 24160)may be implemented as a type of master node capable of self-locating oras a master node without location circuitry. The exemplary ID nodesbeing monitored and used as part of exemplary method 3000 (such as IDnodes 24120 a-24120 f) may be traveling with a respective first portionof packages (e.g., one or more of packages 24400 a-24400 c), have one ormore of them affixed to the outside of one of the packages, have one ormore of them integrated as part of a package, may be deployed within theshipping container without being associated with or fixed to anyparticular one or more of the packages, or may be deployed as part ofmethod 3000 where the ID nodes are disposed in a combined situationwhere some of the ID nodes are associated with particular packages butothers are not while being disposed within the shipping container atdifferent locations in the container.

In more detail and referring now to FIG. 30, method 3000 begins at step3005 where the command node may initially determine which of the IDnodes in the shipping container are anticipated to be broadcastingaccording to a communication profile maintained on the commend node foreach of the ID nodes. For example, exemplary command node 24160 mayaccess profile data 430, which may have a communication profile on eachof ID nodes 24120 a-24120 f Those skilled in the art will appreciatethat the communication profile may be implemented with a single datastructure for all of the ID nodes disposed within the shippingcontainer, or may be implemented in individual data structures per IDnode. In more detail, the communication profile may identify aprogrammatic setting for a broadcast timing parameter that defines whena particular ID node is programmed to transmit an advertising message inthe future to indicate to the command node whether that particular IDnode is anticipated to be broadcasting. In one embodiment, thecommunication profile may define an anticipated broadcast behavior for aparticular one of the ID nodes in the shipping container, so that thecommand node may sense an unanticipated state of ceased broadcasting forthat particular ID node as an inoperative state of that particular IDnode inconsistent with the anticipated broadcast behavior for theparticular ID node. In yet another embodiment, the communication profilemaintained on the command node for each of the ID nodes may define ananticipated broadcast behavior for a respective one of the ID nodes, sothat the command node may sense an unanticipated state of ceasedbroadcasting for that respective ID node based upon such a communicationprofile because the respective ID node is not anticipated to be absentfrom the shipping container (e.g., is not with a package that has beenunloaded from the container) and the sensed inoperative state of therespective ID node is inconsistent with the anticipated broadcastbehavior for the respective ID node per the communication profile. Inthis manner, the communication profile may indicate anticipatedbroadcast behavior for a particular ID node and may in furtherembodiments be used in conjunction with context data (e.g., context data26560), association data (e.g., association data 440), and/or locationdata (e.g., location data 455) so that the command node can appreciate adeeper understanding of the contextual environment for the ID nodes whendetermining which of the ID nodes are anticipated to be broadcasting aspart of method 3000.

At step 3010, method 3000 proceeds with the command node monitoring theID nodes for an unanticipated state of ceased broadcasting from any ofthe ID nodes according to a communication profile maintained on thecommand node for each the ID nodes. In more detail, an embodiment ofmethod 3000 may have the command node in step 3010 monitor those of theID nodes anticipated to be broadcasting (per step 3005 and according tothe communication profile) to identify which of those ID nodes haveceased broadcasting (i.e., are in the unanticipated state of ceasedbroadcasting). This may take the form of monitoring each of the ID nodesthat are anticipated to be broadcasting (per the communication profile)for a shift in broadcast behavior away from the anticipated broadcastbehavior for the respective ID node.

At step 3015, method 3000 continues with the command node identifyingone or more ID nodes in an unanticipated state of ceased broadcastingbased upon the monitoring conducted in step 3010. At step 3020, method3000 proceeds then to have the command node add the identified ID nodeor nodes from step 3015 to a group of ID nodes found by the command nodeto be in the unanticipated state of ceased broadcasting. In thisexemplary manner, the command node senses, detects, or otherwiseidentifies an initial group of one or more of the ID nodes to be in theunanticipated state of ceased broadcasting based upon the monitoringstep 3010.

At step 3025, method 3000 proceeds to have the command node determiningif the size of the group of ID nodes in the unanticipated state ofceased broadcasting exceeds a threshold setting maintained by thecommand node. The threshold setting, a data value maintained in a datastructure (such as a threshold setting value stored as part of CNcontrol and management code 26435 or other data structures used by suchcode (e.g., profile data 430, shared data 445, context data 26560, andthe like)). In more detail, the threshold setting maintained by thecommand node may be kept on the command node's memory as a dynamic valuedefined by the command node based upon a material characteristic of whatis contained in at least one of the packages (e.g., as indicated bypackage information stored in context data 26560 on what is storedwithin shipping container 24300). In a further embodiment, the thresholdsetting may be a dynamic value defined by the command node related to acount of how many of the ID nodes are disposed within the shippingcontainer. For example, if the contents of shipping container 24300 arealtered, the number of ID nodes within shipping container 24300 maydecrease (e.g., an ID node with a package is removed) or may increase(e.g., an ID node with a package is added to the ULD container 24300).Command node 24160 may detect the presence of such a change in ID nodes,some of which may be or may have been part of the group of ID nodesanticipated to be broadcasting. As such, command node 24160 maydynamically update the threshold setting used in step 3025 of anembodiment of method 3000 to reflect such a change in how many ID nodesare now within shipping container 24300.

At step 3030, method 3000 has the command node detecting theenvironmental anomaly when the size of the sensed initial group of theID nodes in the unanticipated state of ceased broadcasting exceeds thethreshold setting maintained by the command node. As such, theenvironmental anomaly detected in step 3030 is based upon monitoringbroadcast behavior instead of being based on the values of sensor data.

A further embodiment, may detect the environmental anomaly as part ofmethod 3000 by also monitoring ID node sensor data broadcast by one ormore of the ID nodes and/or command node sensor data generated onboardthe command node. In more detail, detecting the environmental anomaly inthis further embodiment of step 3030 may involve a combination ofmonitored broadcast behavior and a threshed setting for how many IDnodes are now in an unanticipated state of ceased broadcasting as wellas when an environmental condition for one or more of the ID nodesand/or packages exceeds a relevant environmental threshold condition forthe ID node/package as indicated by sensor data. As such, this furtherembodiment of method 3000 expands upon the detection scheme at step 3030to be multi-variate, which in yet a further embodiment may also beimplemented in a dynamic aspect of the command node's operation—e.g.,the command node may initially operate to detect an environmentalanomaly by monitoring broadcast behavior as described above, but oncethe threshold setting is exceeded, the command node may verify orconfirm the environmental detection using one or more types of sensordata generated by one or more of the ID nodes and/or the command nodeitself.

In a further embodiment of step 3030 of method 3000, the detectedenvironmental anomaly for the shipping container may be detected as afire within the shipping container based upon how quickly the sensedinitial group of the ID nodes have changed broadcast behavior whenmonitoring the ID nodes and detecting the environmental anomaly. Forexample, command node 24160 may use its timer 26460 as part of step 3025to monitor the rate of how quickly the ID nodes are identified in steps3015 and 3020 as an indicator of how quickly the sensed initial group ofthe ID nodes have changed broadcast behavior up to the point the sizeexceeds the threshold setting in step 3025. The indication that theenvironmental anomaly is a fire may be reported as part of the layeredalert notification generated as explained below in step 3035.

In yet another embodiment of step 3030 of method 3000, the detectedenvironmental anomaly for the shipping container may be detected as afire within the shipping container based upon which of the ID nodes arein the sensed initial group of the ID nodes and based upon materialcontained in at least one of packages associated with the sensed initialgroup of the ID nodes as indicated in the context data related to thesensed initial group of the ID nodes. For example, command node 24160may access context data 26560 to identify the type of material containedwithin the shipping container (or material contained in one of thepackages associated with an unresponsive one of the ID nodes) and usethis information to further detect that the environmental anomaly is afire based on that material information. The indication that theenvironmental anomaly is a fire may then be reported as part of thelayered alert notification generated as explained below in step 3035.

In still another embodiment of step 3030 of method 3000, the detectedenvironmental anomaly for the shipping container may be detected as afire within the shipping container based upon where the sensed initialgroup of the ID nodes are located within the shipping containeraccording to the context data related to the sensed initial group of theID nodes and a loading scheme for the shipping container, the loadingscheme being maintained in the command node. For example, command node24160 may access context data 26560 to identify the location of aparticular ID node(s) as well as a loading scheme for what is storedwithin the shipping container and use this information to further detectthat the environmental anomaly is a fire based on that information.Again, the indication that the environmental anomaly is a fire may thenbe reported as part of the layered alert notification generated asexplained below in step 3035.

In another embodiment of step 3030 of method 3000, the detectedenvironmental anomaly for the shipping container may be detected as anexplosion within the shipping container. In more detail, this may bebased upon how quickly the sensed initial group of the ID nodes havechanged broadcast behavior when monitoring the ID nodes and detectingthe environmental anomaly, or how quickly the sensed initial group ofthe ID nodes have changed broadcast behavior when monitoring the IDnodes and based upon material contained in at least one of packagesassociated with the sensed initial group of the ID nodes as indicated inthe context data related to the sensed initial group of the ID nodes.The indication that the environmental anomaly is an explosion may bereported as part of the layered alert notification generated asexplained below in step 3035.

At step 3035, method 3000 proceeds with the command node generating alayered alert notification related to the detected environmental anomalyfor the shipping container. In this step as part of method 3000, thegenerated layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority based upon a size of the sensed initialgroup of the ID nodes and context data related to the sensed initialgroup of the ID nodes (e.g., context data 26560 being maintained locallyon the command node 26000 as shown in FIG. 26).

In more detail, the command node may generate the layered alertnotification in step 3035 based upon which of the ID nodes are (a)sensed to be part of the initial group of ID nodes in the unanticipatedstate of ceased broadcasting and (b) indicated by the context datarelated to the sensed initial group of the ID nodes to be stillmaintained within the shipping container. In another embodiment, thecommand node may generate the layered alert notification in step 3035based upon how quickly the sensed initial group of the ID nodes havechanged broadcast behavior when detecting the environmental anomaly. Instill another embodiment, the command node may generate the layeredalert notification as part of step 3035 based upon where the sensedinitial group of the ID nodes are located within the shipping containeraccording to the context data related to the sensed initial group of theID nodes.

A more detailed embodiment of step 3035 may involve patterns of sensedunresponsive ID nodes. For example, the sensed initial group of the IDnodes may form a first sensed pattern of unresponsive ID nodes. Thecommand node may then sense a subsequent group of one or more ID nodesto be in the unanticipated state of ceased broadcasting after thecommand node senses the initial group of the ID nodes in theunanticipated state of ceased broadcasting where the subsequent group ofID nodes is larger than the initial group of the ID nodes. The commandnode may then, as part of this further embodiment of method 3000, detecta further environmental anomaly when a pattern of the subsequent groupof the ID nodes in the unanticipated state of ceased broadcastingexceeds a threshold pattern setting maintained by the command node whencompared to the first sensed pattern of unresponsive ID nodes. In such asituation, this further embodiment of method 3000 may have the commandnode generating the layered alert notification as being based upon thesize of the sensed initial group of the ID nodes, a size of thesubsequent group of the ID nodes, a change in the pattern of thesubsequent group of the ID nodes and the pattern of the initial group ofthe ID nodes, and context data related to the subsequent group of the IDnodes.

As part of step 3035, the targeted mediation recipient may be identifiedmore specifically. For example, in one embodiment, the targetedmediation recipient may be automatically selected by the command nodebased upon an extent of how much the size of the sensed initial group ofID nodes exceeds the threshold setting. Thus, if the size of the initialgroup of unresponsive ID nodes is 25 and the threshold setting is 5, thecommand node may responsively and automatically select the targetedmediation recipient to be a fire suppression system where if the groupof unresponsive ID nodes is 6 and the threshold setting is 5, thecommand node may select the targeted mediation recipient to be alogistics crew member of the transit vehicle that can inspect theshipping container.

As such, a further embodiment may have the targeted mediation recipientidentified by the command node in the layered alert notification to be,for example, a fire suppression system operative to automaticallyrespond to the detected environmental anomaly based upon receipt of thelayered alert notification, an operator of the transit vehicle that canalter movement of the transit vehicle, or a logistics crew member of thetransit vehicle that can inspect the shipping container.

As such, a further embodiment of method 3000 may further include thestep of automatically dispensing, by the fire suppression system, firesuppression agent into the shipping container upon receipt of a triggermessage from the external transceiver of the transit vehicle, where thetrigger message being in response to the layered alert notification. Inmore detail, the trigger message from the external transceiver may beautomatically generated by the external transceiver, or may be generatedin response to input to the external transceiver from a logistics crewmember of the transit vehicle after inspecting the shipping container.In an embodiment where the external transceiver is part of the firesuppression system, method 300 may further include the step of havingthe command node directly cause the fire suppression system toautomatically dispense the fire suppression agent into the shippingcontainer via the layered alert notification operating as the triggermessage for the fire suppression system.

As part of step 3035, the targeted mediation action may also beidentified more specifically. For example, the targeted mediation actionmay be automatically selected by the command node based upon which ofthe ID nodes are sensed to be the initial group of ID nodes in theunanticipated state of ceased broadcasting; based upon how quicklymembers of the sensed initial group of the ID nodes have changedbroadcast behavior to become in the unanticipated state of ceasedbroadcasting; based upon a pattern of change when the initial group ofthe ID nodes is monitored and sensed to have changed broadcast behaviorto become in the unanticipated state of ceased broadcasting; and/orbased upon where the sensed initial group of the ID nodes are locatedwithin the shipping container according to the context data related tothe sensed initial group of the ID nodes.

When identifying the targeted mediation action as part of the layeredalert notification in step 3035, the command node may consider furthercontextual types of information, such as vehicle status data, containerstatus data, geolocation data, and/or facility status data. For example,a further embodiment of method 3000 may have the command node receivingvehicle status data provided by the external transceiver unit associatedwith the transit vehicle. In this situation, the command node mayidentify the targeted mediation action in the layered alert notificationas part of step 3035 depending upon a state of the transit vehicle asindicated by the vehicle status data (e.g., a takeoff vehicular status,a cruising vehicle status, a landing vehicular status, and a stationaryvehicular status of the transit vehicle). Thus, when the vehicle ismoving (i.e., cruising vehicle status), the command node may considerthis data input to enhance and improve what targeted mediation action toidentify, which may be entirely different from when the vehicle isstationary. In another example, a further embodiment of method 3000 mayhave the command node accessing container status data maintained by thecommand node and associated with the shipping container. In thissituation, the targeted mediation action identified by the command nodein the layered alert notification as part of step 3035 may depend upon astate of the shipping container as indicated in the container statusdata (e.g., a loading status, an unloading status, a secure status, anin-transit status). In still another example, a further embodiment ofmethod 3000 may have the command node accessing geolocation data (e.g.,a type of location data 455) maintained by the command node, associatedwith the shipping container, and related to a current location of theshipping container. In this situation, the targeted mediation actionidentified by the command node in the layered alert notification as partof step 3035 may depend upon the current location of the shippingcontainer as indicated in the geolocation data. In still anotherexample, a further embodiment of method 3000 may have the command nodeaccessing facility status data maintained by the command node andassociated with a storage facility for the shipping container. In thissituation, the targeted mediation action identified by the command nodein the layered alert notification as part of step 3035 may depend upon astate of the storage facility as indicated in the facility status data.

Further still, embodiments of step 3035 of method 3000 may identify thetargeted mediation action an automatic response by a triggered firesuppression system on the transit vehicle; a prompted request to changecourse of the transit vehicle from an existing travel path of thetransit vehicle and/or a prompted request to investigate the shippingcontainer.

More detailed embodiments of step 3035 of method 3000 may have themediation response priority automatically selected by the command nodebased upon an extent of how much the size of the sensed initial group ofID nodes exceeds the threshold setting. For example, the mediationresponse priority established by the command node as part of the layeredalert notification in step 3035 may be an immediate priority level thatautomatically indicates further travel by the transit vehicle ispermissible when responding to the detected environmental anomaly or maybe a higher priority level that automatically indicates further travelby the transit vehicle is not permissible and requests immediatecessation of transit vehicle travel.

At step 3040, method 3000 proceeds with the command node transmittingthe layered alert notification to the transceiver unit to initiate amediation response related to the targeted mediation action. Again, insome embodiments, the transceiver unit may be separate from the targetedmediation recipient (e.g., a fire suppression system onboard thevehicle) but the transceiver unit in other embodiments may be built intosuch onboard devices related to the targeted mediation recipients (e.g.,display units in a cockpit or logistics support area of the transitvehicle).

Additional embodiments of exemplary method 3000 may involve morespecific details and/or additional steps. For example, monitoring forunresponsive ID nodes as part of step 3010 may, in more detail, involvemonitoring a select subset of the ID nodes for the unanticipated stateof ceased broadcasting from any of the ID nodes in the select subsetaccording to a communication profile maintained on the command node foreach the ID nodes in the select subset. This select subset may be lessthan all of the ID nodes anticipated to be broadcasting and, as such,provides a further level of improved selective targeting of whichparticular ID nodes to use when monitoring for broadcast behavioralchanges in step 3010. As such, the command node may then sense theinitial group of one or more unresponsive ID nodes from the selectsubset of ID nodes monitored (that should be broadcasting) and detectthe environmental anomaly when the size of the sensed initial group ofthe ID nodes in the unanticipated state of ceased broadcasting exceedsthe threshold setting maintained by the command node. In this example,the threshold setting maintained by the command node may be a dynamicvalue defined by the command node based upon a material characteristicof what is contained in at least one of the packages and/or a dynamicvalue defined by the command node related to a count of how many of theID nodes are in the select subset of ID nodes.

In a further embodiment of method 3000, the communication profile foreach of the ID nodes may be used by the command node to regulate howoften each of the ID nodes broadcast. As such, method 3000 may alsoinclude the command node instructing each of the ID nodes not in theinitial group of the ID nodes (the initial group being those of the IDnodes anticipated to be broadcasting that have been found unresponsive)to broadcast at a second messaging rate that exceeds an initialmessaging rate after method 3000 has the command node transmitting thelayered alert notification to the transceiver unit. In this way, each ofthe ID nodes not in the initial group of the ID nodes more frequentlybroadcast compared to prior to when the initial group of the ID nodeswas sensed to be in the unanticipated state of ceased broadcasting. Inmore detail, the initial messaging rate for the ID nodes may be aninitial value correlated to an environmental risk associated with atleast one of the packages within the shipping container. Further, thesecond messaging rate for the ID nodes not in the initial group of theID nodes may be a predetermined higher messaging rate based upon a typeof material existing within at least one of the packages within theshipping container.

In yet another embodiment of method 3000, the command node may beremotely updated with threshold updates for the threshold settingmaintained by the command node. For example, such a threshold update maybe received by the command node from the external transceiver unit wheresuch an update may be defined by an operator of the transit vehicleusing the external transceiver unit, or a logistics crew member of thetransit vehicle using the external transceiver unit. In another example,the threshold update may be provided to the external transceiver unitfrom a remote control center in communication with the externaltransceiver unit.

In like manner, a further embodiment of method 3000 may have the commandnode receiving a selection update for which of the ID nodes are includedin the select subset of the ID nodes described above. Such a selectionupdate may be received from the external transceiver unit (e.g., asdefined by an operator of the transit vehicle using the externaltransceiver unit or a logistics crew member of the transit vehicle usingthe external transceiver unit) or from a remote control center incommunication with the external transceiver unit.

In still a more detailed embodiment of method 3000, step 3010 involvingmonitoring those ID nodes anticipated to be broadcasting may be furtherimplemented to confirm validity of broadcasts received from those IDnodes. In more detail, step 3010 may have the command node (a) receivinga communication broadcasted from a first of the ID nodes; (b) confirmingthe validity of the received communication; (c) having the command noderepeat steps (a) and (b) for the remainder of the communicationsreceived from any of the remaining ones of the ID nodes; and then havingthe command node sensing the initial group of one or more of the IDnodes to be in the unanticipated state of ceased broadcasting based uponthe command node determining which of the ID nodes are not broadcastingbased upon steps (a)-(c). Step (b) of confirming may, in someembodiments, be an active type of confirmation where the command node issending an authentication request to the first of the ID nodes, andreceives a validation response from that ID node that authenticates thecommunication broadcasted from the first of the ID nodes. Alternatively,step (b) of confirming may, in other embodiments, be passive in that thecommand node may be accessing a validation sequence for the first of theID nodes (where the validation sequence is maintained by the commandnode and characterizing expected broadcasts from the first of the IDnodes) and determining if the received communication from the first ofthe ID nodes matches a predetermined one of the expected broadcasts fromthe first of the ID nodes according to the validation sequence storedwithin the command node. Such a predetermined one of the expectedbroadcasts may be a rotating value previously received by the commandnode for the first of the ID nodes.

Those skilled in the art will appreciate that method 3000 as disclosedand explained above in various embodiments may be implemented using anexemplary improved monitoring system for detecting an environmentalanomaly in a shipping container that maintains multiple packages and forreporting a layered alert notification related to the environmentalanomaly to an external transceiver unit associated with a transitvehicle transporting the shipping container such as that explained abovewith reference to FIG. 24C and its exemplary elements. Such anembodiment of an improved monitoring system, as explained above relativeto operations according to method 3000 and with elements from FIG. 24C,uses at least multiple ID nodes disposed within the shipping container(e.g., ID nodes 24120 a-24120 f) running one or more ID node monitoringprogram code as part of node control and management code 325 to controloperations of the ID nodes to broadcast wireless signals (e.g.,advertising signals that may include other information, such as sensordata), as well as a command node mounted to the shipping container(e.g., command node 24160 in FIG. 24C) running one or more parts of CNcontrol & management code 26425 to control the operations of the commandnode as part of monitoring for and detecting an environmental anomalybased on unanticipated ID nodes that cease broadcasting (e.g., as per acommunication profile for the ID node) as well as generating the layeredalert notification and transmitting that notification to the externaltransceiver unit to initiate a type of mediation response. Such code maybe stored on a non-transitory computer-readable medium, such as memorystorage 26415 on command node 24160 (an embodiment of exemplary commandnode 26000) and memory storage 315 on ID nodes 24120 a-24120 f(embodiments of exemplary ID node 120 a). Thus, when executing suchcode, the ID nodes and the command node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 3000 and variations of that method.

External and Internal Monitoring for an Environmental Anomaly

Further embodiments may address enhanced detection of an environmentalanomaly relative to a shipping container being transported on a transitvehicle in situations where an exemplary command node (e.g., ULDcontainer node that is essentially a master node that may not havelocation circuitry for self-locating capabilities, a mobile master nodedeployed on or as part of the shipping container that has locationcircuitry for self-locating capabilities) may more broadly monitor whatID nodes are anticipated to be broadcasting within as well as around theshipping container. In particular, embodiments may deploy a container'scommand node to monitor ID nodes within and external to the shippingcontainer and detect whether there is a shift in behavior for those IDnodes anticipated to be broadcasting regardless of whether the ID nodesare actually within the command node's own shipping container ordisposed external to the shipping container but still within thecommunication range of the command node (i.e., the command node beingcapable of receiving communications from such an externally disposed IDnode). Such a shift in behavior may be detected and take the form of,for example, an unanticipated state of ceased broadcasting from amonitored ID node that is anticipated to be broadcasting—whether withinthe shipping container or outside the shipping container. The cessationof broadcasting by particular ID nodes, both from within the shippingcontainer as well as disposed outside of but near the shippingcontainer, may operate as a detectable trigger condition indicating anenvironmental anomaly for the shipping container, such as a fire withinthe shipping container.

In such embodiments, an ID node being monitored may be considered a“package ID node” when the ID node is attached to, disposed within,travels with, or is otherwise associated as part of a package beingtransported on and within the temporary custody of the transit vehicle(such as an aircraft). For example, exemplary ID node 24120 a shownwithin package 24400 d in FIG. 24B may be considered an exemplarypackage ID node given that ID node 24120 a in FIG. 24B is disposedwithin the package itself or may be integrated as part of the package(e.g., part of the packaging material, cushioning material, fillmaterial, and the like). Alternatively, an exemplary ID node beingmonitored may be considered a “non-package ID node” when the ID node isnot specifically attached to, disposed within, traveling with, nor isotherwise associated as part of a particular package or group ofpackages being transported on the transit vehicle. For example,exemplary ID node 24120 a shown in FIG. 24C may be considered anexemplary non-package ID node given that it may simply be disposedwithin the shipping container (such as on a wall, on the floor, attachedto the ceiling, fixed to a door, or simply placed within the interiorstorage area of the shipping container along with one or more packages)and not specifically associated with nor attached to any particularpackage or group of packages being transported on the transit vehicle.

As explained in more detail below, such embodiments may involve systemsand methods where the ID nodes being monitored are package ID nodesassociated with particular packages or, alternatively, are the ID nodesbeing monitored as non-package ID nodes. In more detail, furtherembodiments may have the command node monitoring a set of ID nodeswithin the shipping container where some are package ID nodes and somemay be non-package ID nodes while also monitoring another set of IDnodes outside the shipping container where those monitored ID nodesoutside the shipping container include both package ID nodes andnon-package ID nodes. Additional embodiments may further vary thisconfiguration of ID nodes being monitored by the command node—e.g.,monitoring only package ID nodes within the container while alsomonitoring only non-package ID nodes outside the container; monitoringonly non-package ID nodes within the container while also monitoringonly package ID nodes outside the container. Further still, theconfiguration of ID nodes being monitored in embodiments may be furtherdiversified as, for example, monitoring only package ID nodes within thecontainer while also monitoring a combination of package and non-packageID nodes outside the container; monitoring only non-package ID nodeswithin the container while also monitoring a combination of package andnon-package ID nodes outside the container; monitoring a combination ofpackage and non-package ID nodes within the container while alsomonitoring only package ID nodes outside the container; and monitoring acombination of package and non-package ID nodes within the containerwhile also monitoring only non-package ID nodes outside the container.

FIGS. 31-34 illustrate various embodiments of different exemplarysystems and their components where a command node may monitor differenttypes of ID nodes within and external to a shipping container andresponsively interact with an external transceiver on the transitvehicle as well as directly interact with an onboard fire suppressionsystem on the transit vehicle. In more detail, FIG. 31 is a diagram ofan exemplary wireless node network used for detecting environmentalanomalies using a command node associated with a shipping containerbeing transported on a transit vehicle and ID nodes internal andexternal to the shipping container on the transit vehicle and where theID nodes are each associated with packages in accordance with anembodiment of the invention. Referring now to FIG. 31, exemplary system32000 is illustrated showing transit vehicle 24200 having transitvehicle storage 24205 that maintains temporary custody of differentshipping containers, such as container 24300 a and 24300 b (e.g., ULDcontainers, and the like), when transporting them. The transit vehicle24000 is further equipped with an external transceiver 24150 onboardalong with an exemplary onboard fire suppression system 25010 disposedin the transit vehicle storage 24205. The onboard fire suppressionsystem 25010 may be activated by the external transceiver 24150 and/or acommand node of a particular shipping container to supply firesuppression agent into one or more shipping containers (e.g., containers24300 a, 24300 b) as well as into the transit vehicle storage 24205 insome embodiments (e.g., as an additional mediation response to adetected environmental anomaly related to a shipping container).

In FIGS. 31, 33, and 34, the exemplary external transceiver 24150 isdisposed on transit vehicle 24200 (similar to that shown in theembodiments of FIGS. 24A-24C) and may receive alert notifications andautomatically respond to such alerts by initiating a mediation responserelated to a particular mediation action based upon the particularenvironmental anomaly detected. Some responses may have the externaltransceiver 24150 triggering the onboard fire suppression system 25010on transit vehicle 24200 and/or communicating with an operator orlogistics crew aboard transit vehicle 24200 as explained above.Exemplary external transceiver 24150 shown in FIGS. 31, 33, and 34 mayalso communicate with remote control center server 24100 over network24105 to report the detected environmental anomaly and any mediationresponse initiated as well as to receive information about packagesonboard the transit vehicle (e.g., packages 24400 a-24400 h),environmental threshold conditions related to such packages, and otherupdated data to be used for detecting environmental anomalies andinitiating responsive mediation actions.

In general, the exemplary onboard fire suppression system 25010 shown inFIGS. 31, 33, and 34 is similar to that described above relative to FIG.25B in that it may be selectively activated with an activation controlsignal to the fire suppression system's controller, which then causes afire suppression agent to be applied to a shipping container. In oneembodiment, the fire suppression system's controller responds byconnecting with a particular shipping container and initiatespressurized expulsion of a fire suppression agent from a firesuppression agent reservoir chamber into that particular shippingcontainer on the transit vehicle 24200. In a more detailed embodiment,this may occur using an articulating puncture (e.g., an actuator andarticulating needle) responsive to the fire suppression system'scontroller that forcibly creates an opening in a surface of theparticular shipping container and through which the fire suppressionagent may flow into the shipping container so as to address a detectedenvironmental anomaly within that particular shipping container.

FIGS. 32A-32C provide further details on such an exemplary onboard firesuppression system through a series of diagrams of such an exemplaryfire suppression system that may be activated and deployed on a transitvehicle for initiating a mediation action in response to a detectedenvironmental anomaly related to a shipping container being transportedon the transit vehicle in accordance with an embodiment of theinvention. Referring now to FIG. 32A, exemplary fire suppression system25010 (as generally discussed above) is shown in more detail as disposedon transit vehicle 24200. In this embodiment, the system 25010 generallyincludes at least a fire suppression controller 32000, a transceiver32010 coupled to the controller, a pump 32015, a fire suppression agentreservoir chamber 32020 that holds a fire suppression agent, andactuators 32025 a-32025 b that responsively control an articulatingneedle 32030 a-32030 b as a type of dispenser coupled to the pump andthat may be extended to puncture a shipping container 24300 a on thetransit vehicle 24200. An exemplary fire suppression controller 32000may be implemented as a control circuit (e.g., a logic circuit, PLA, orprogrammable microprocessor-based controller board with memory,processing, interface circuitry, and drivers) that receives theactivation control signal through transceiver 32010 to control operationof the system 25010. The transceiver 32010 may be implemented as a wiredand/or wireless transceiver operative to receive an activation controlsignal from, for example, external transceiver 24150 on the transitvehicle and/or from a shipping container's command node (e.g., commandnode 24160 disposed as part of shipping container 24300 a). Exemplarytransceiver 32010 may also be operative to transmit status informationfrom controller 32000 related to the state of the system (e.g., statusof the fire suppression agent within reservoir chamber 32020, positionof an actuator 32025 a and its linked articulating needle 32030 a, aswell as pump status, pressure readings, and flow rates as sensed bysensors (not shown), and the like).

Exemplary pump 32015 may be implemented as an electronically activatedpump to move the fire suppression agent from fire suppression agentreservoir chamber 32020 to one or more of the actuator/needledispensers. Such an exemplary pump 32015 may include one or moreselectively controlled valves to direct the output of the pump to aparticular actuator/needle dispenser so that the pressurized firesuppression agent is selectively provided one or more of theactuator/needle dispensers associated with particular shippingcontainer(s) on the transit vehicle 24200 in response to control signalssent to pump 32015 from controller 32000. Some embodiments may implementpump 32015 with multiple pumps that may be dedicated for particularsections of transit vehicle storage 24205 or for particular shippingcontainers or groups of shipping containers on the transit vehicle24200. In this way, the system's fire suppression agent pump 32015 maybe activated by the fire suppression controller 32000 in response to theactivation control signal provided to the controller 32000 (e.g., asreceived by the fire suppression transceiver 32010 and passed tocontroller 32000, which then generates the appropriate control signalsto send to pump 32015 based on the contents of the activation controlsignal that identify which shipping container requires a mediationresponse by the fire suppression system 25010, what pressure may berequired, how long to apply the fire suppressant agent, and othercontrol parameters of pump 32015 needed to provide the appropriatemediation response).

In some embodiments, fire suppression agent reservoir chamber 32020 maybe implemented as non-pressurized container where the fire suppressionagent flows from the chamber 32020 simply by virtue of gravity andsuction from the pump 32015, which then pressurizes the fire suppressionagent as it flows to the shipping container through the particularactuator/needle dispenser. In other embodiments, fire suppression agentreservoir chamber 32020 may be loaded with fire suppression agentmaterial maintained under a particular storage pressure (i.e.,pressurized on chamber 32020). As such, the combination of a pressurizedrelease from chamber 32020 and the action of pump 32015 allows the firesuppression agent to flow to the shipping container through theparticular actuator/needle dispenser.

The actuators 32025 a-32025 b and needles 32030 a-32030 b provide anarticulating puncture coupled to the fire suppression agent reservoirchamber 32020 that effectively dispense and allow for selectiveinjection of pressurized fire suppression agent into a particularshipping container on the transit vehicle 24200. Those skilled in theart will appreciate that actuators 32025 a-32025 b may be implementedwith hydraulically and/or mechanically actuated linkages, arms, pistons,or other articulating structure that moves needles 32030 a-32030 b.Exemplary needles 32030 a-32030 b may be implemented with material ofsufficient stiffness and strength to puncture the exterior of a shippingcontainer used in an embodiment and have an input side coupled to thepump 32015 and output hole near the tip of the needle that extends intothe shipping container when the needle is deployed into the shippingcontainer.

In an embodiment, each of the actuators 32025 a-32025 b are coupled toand may be activated by the fire suppression system controller 32000 sothat a particular actuator, such as actuator 32035 a, responsivelyarticulates, moves, and/or extends its needle 32030 a from a retractedposition (as shown in FIG. 32A) to an extended activated position (asshown in FIG. 32B). In this way, the extended needle 32030 a and itsactuator 32025 a are forcibly deployed to rapidly create an opening in ashipping container (e.g., shipping container 24300 a shown in FIGS.32A-32C) in response to a deployment control signal sent from the firesuppression controller 32000 to the respective actuator (e.g., actuator32025 a) in response to the activation control signal received by thefire suppression controller 32000 via transceiver 32010. Once thedispensing articulated puncture (e.g., actuator 32025 a and its relatedneedle 32030 a) is in the extended activated position as shown in FIG.32B, fire suppression controller 32000 may send the appropriate controlsignals to pump 32015 based on the contents of the activation controlsignal, which identifies which shipping container requires a mediationresponse by the fire suppression system 25010 (e.g., control signalsfrom controller 32000 to pump 32015 to selectively supply firesuppression agent from chamber 32020 to needle 32030 a so that thepressurized fire suppression agent is injected within shipping container24300 a). Thus, as shown in FIG. 32C, fire suppression agent 32040pressurized by pump 32015 may be supplied from fire suppression agentreservoir chamber 32020, then through needle 32030 b so that the agententers shipping container 24300 a as a type of mediation action orresponse that may be directly or indirectly initiated by a shippingcontainer's command node 24160.

While the embodiments shown in FIGS. 32A-32C illustrate exemplaryonboard fire suppression system 25010 illustrate a system that mayselectively dispense fire suppression agent into one or more differentshipping containers being transported on transit vehicle 24200, furtherembodiments of onboard fire suppression system may be implemented asdedicated modules (similar to what is shown in FIG. 25B) that are eachan onboard fire suppression system paired to a particular shippingcontainer. Thus, further embodiments may deploy multiple dedicatedonboard fire suppression systems that service and can respond todetected environmental anomalies in one or more different shippingcontainers where the shipping container's command node 24160 and/ortransit vehicle's external transceiver 24150 may interact with more thanone onboard fire suppression system.

As shown in FIGS. 31, 33, and 34, exemplary transit vehicle storage24205 is shown maintaining the temporary custody of shipping containers24300 a and 24300 b. Those skilled in the art will appreciate that whileeach of these shipping containers may have an associated command node,the illustrations in FIGS. 31, 33, and 34 focus on embodiments withhighlighted details of exemplary command node 24160 mounted to shippingcontainer 24300 a and ID nodes that may be monitored by exemplarycommand node 24160 in different example embodiments.

Further, as shown in FIGS. 31, 33 and 34, exemplary transit vehiclestorage 24205 may temporarily maintain a variety of different packageswhere each package may or may not be within particular shippingcontainers in the transit vehicle storage 24205 and the packages may ormay not be associated with a specific ID node. For example, as shown inFIG. 31, the ID nodes within the transit vehicle storage 24205 are eachassociated with particular packages in accordance with an embodiment ofthe invention. In particular, as shown in FIG. 31, transit vehiclestorage 24205 has packages 24400 a, 24400 b (and their respective IDnodes 24120 a, 24120 b) disposed within the transit vehicle storage24205 but outside of both shipping container 24300 a and shippingcontainer 24300 b but situated close to shipping container 24300 a.Packages 24300 c-24400 e (and their respective ID nodes 24120 c-24120 e)are disposed within shipping container 24300 a while packages 24400f-24400 h (and their respective ID nodes 24120 f-24120 h) as disposedwithin shipping container 24300 b, which is next to shipping container24300 a. Those skilled in the art will appreciate that ID nodes 24120a-24120 h shown in FIG. 31 are within a communication range of commandnode 24160 and, thus, able to generate wireless broadcasts that may bereceived by command node 24160.

In another example configuration shown in FIG. 33, the ID nodes withinthe transit vehicle storage 24205 are not specifically associated withpackages in accordance with another embodiment of the invention. Inparticular, as shown in FIG. 33, transit vehicle storage 24205 haspackages 24400 c-24400 e disposed within shipping container 24300 a butnone of ID nodes 24120 c-24120 e within shipping container 24300 a arespecifically associated with any of packages 24400 c-24400 e in thecontainer. Additionally, ID nodes 24120 a-24120 b are non-package IDnodes disposed outside of shipping container 24300 a and shippingcontainer 24300 b but situated close to shipping container 24300 a.Non-package ID nodes 24120 g-24120 i are disposed within shippingcontainer 24300 b, which is next to shipping container 24300 a. The IDnodes not specifically associated with any package but disposed within ashipping container (such as ID nodes 24120 c-24120 i) may be implementedas standalone devices loaded into a particular shipping container butnot attached, affixed, or otherwise specifically associated with aparticular package in the container; integrated as part of the shippingcontainer (e.g., as part of the walls, floor, ceiling, door, and thelike), or merely attached to part of the shipping container. As with theconfiguration shown in FIG. 31, those skilled in the art will appreciatethat ID nodes 24120 a-24120 h shown in FIG. 33 are within acommunication range of command node 24160 and, thus, able to generatewireless broadcasts that may be received by command node 24160.

In still another example configuration shown in FIG. 34, the ID nodeswithin the transit vehicle storage 24205 are a combination of package IDnodes and non-package ID nodes within and outside of a particularshipping container in accordance with an embodiment of the invention. Inmore detail, as shown in FIG. 34, transit vehicle storage 24205 haspackages 24400 c-24400 e disposed within shipping container 24300 a. Inthis example, packages 24400 c and 24400 e have associated ID nodes24120 c and 24120 e, respectively, while ID nodes 24120 d and 24120 fare not specifically associated with any of packages 24400 c-24400 e inthe container. Additionally, ID nodes 24120 a-24120 b are package IDnodes respectively associated with packages 24400 a-24400 b disposedoutside of shipping container 24300 a and shipping container 24300 b butsituated close to shipping container 24300 a. Non-package ID nodes 24120g-24120 i are disposed within shipping container 24300 b, which is nextto shipping container 24300 a. Again, the ID nodes not specificallyassociated with any package but disposed within a shipping container(such as ID nodes 24120 d and 24120 f-24120 i) may be implemented asstandalone devices loaded into a particular shipping container but notattached, affixed, or otherwise specifically associated with aparticular package in the container; integrated as part of the shippingcontainer (e.g., as part of the walls, floor, ceiling, door, and thelike), or merely attached to part of the shipping container. As with theconfiguration shown in FIGS. 31 and 33, those skilled in the art willappreciate that the combination of package and non-package ID nodes24120 a-24120 h shown in FIG. 33 are within a communication range ofcommand node 24160 and, thus, able to generate wireless broadcasts thatmay be received by command node 24160.

FIG. 35 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using awireless node network having at least a command node associated with ashipping container and ID nodes within the shipping container andoutside the shipping container and where the ID nodes are notspecifically associated with packages in accordance with an embodimentof the invention. In particular, FIG. 35 describes an exemplary improvedmethod 3500 for monitoring for an environmental anomaly related to ashipping container (e.g., shipping container 24300 a) using a wirelessnode network. The shipping container involved in method 3500 is beingtransported on a transit vehicle (e.g., transit vehicle 24200—such as anaircraft, railway conveyance, a maritime vessel, or a roadwayconveyance) that also transports multiple packages (e.g., packages 24400a-24400 h as shown in FIG. 31). The wireless node network involved inmethod 3500 has at least a plurality of ID nodes (e.g., ID node 24120a-24120 h as shown in FIG. 31) and a command node associated with theshipping container (e.g., command node 241260 associated with andmounted to shipping container 24300 a). The command node used as part ofmethod 3500 may, for example, be implemented as a container nodeintegrated as part of the shipping container or a self-locating masternode implemented separately from the shipping container. The ID nodesused as part of method 3500 include a first set of the ID nodes disposedwithin the shipping container (e.g., ID nodes 24120 c-24120 e) and asecond set of the ID nodes disposed outside the shipping container(e.g., ID nodes 24120 a, 24120 b, and 24120 f-24120 h). In thisconfiguration, the command node involved in method 3500 is operative tocommunicate with each of the ID nodes in the first set of the ID nodesand the second ID nodes and an external transceiver unit associated withthe transit vehicle (e.g., external transceiver 24150 on transit vehicle24200).

Referring now to FIG. 35, exemplary method 3500 begins at step 3505 withthe command node determining which of the ID nodes disposed in and nearthe shipping container are anticipated to be broadcasting according to acommunication profile on what ID nodes are within and located near theshipping container. For example, command node 24160 may referenceprofile data 430 (as well as location data and/or association data) thatmay indicate what ID nodes are within shipping container 24300 a orloaded within transit vehicle storage 24205. Using this information,command node 24160 may initiate communication with any ID nodes withinthe command node's transmission and reception range (e.g., what ID nodesmay receive communications from command node 24160 and which ID nodesrespond to such communications from the command node 24160). Those IDnodes that may establish initial communications with command node24160—i.e., ID nodes within shipping container 24300 a and outside of24300 a—may be identified as potential ID nodes to be monitored as partof the embodiment of method 3500 as long as the communication profileinformation on each of those potential ID nodes indicates the particularID node is anticipated to be broadcasting so that the command node 24160is able to count on communications from those ID nodes anticipated to bebroadcasting under normal conditions.

At step 3510, method 3500 continues with the command node monitoring foran unanticipated state of ceased broadcasting from any of the ID nodeswithin the first set of the ID nodes disposed within the shippingcontainer according to a communication profile for each the ID nodes inthe first set of the ID nodes maintained on the command node, as well asmonitoring for an unanticipated state of ceased broadcasting from any ofthe ID nodes within the second set of the ID nodes disposed outside theshipping container according to a communication profile for each the IDnodes in the second set of the ID nodes. For example, command node 24160shown in FIG. 31 may monitor the first set of ID nodes (e.g., ID nodes24120 c-24120 e disposed within shipping container 24300 a) as well asmonitor the second set of ID nodes (e.g., ID nodes 24120 a, 24120 b, and24120 f-24120 h disposed outside shipping container 24300 a). Commandnode 24160 would be monitoring those ID nodes in particular as part ofstep 3510 because the communication profile data on each of those nodes(as indicated in profile data 430 on command node 24160) indicates theyare anticipated to be broadcasting.

At step 3515, method 3500 continues by identifying one or more ID nodesfrom the first set and/or second set of the monitored ID nodes as beingunresponsive or in an unanticipated state of ceased broadcasting. Inmore detail, this may have the command node detecting an unresponsivegroup of the ID nodes to be in the unanticipated state of ceasedbroadcasting based upon the monitoring step for the first set of the IDnodes and upon the monitoring step for the second set of the ID nodes.The command node, such as command node 24160, may then determine if theunresponsive group of the ID nodes includes any from the first set ofthe ID nodes (i.e., those monitored ID nodes disposed within theshipping container) and if the unresponsive group of the ID nodesincludes any from the second set of the ID nodes (i.e., those monitoredID nodes disposed external to the shipping container).

At step 3520, method 3500 continues with the command node adding any ofthe identified ID nodes from step 3515 to a group of ID nodes in theunanticipated state of ceased broadcasting. Then, at decision step 3525,method 3500 has the command node determining if the size of the group ofID nodes in the unanticipated state of ceased broadcasting exceeds athreshold setting maintained by the command node. If so, method 3500proceeds from step 3525 directly to step 3530 where the command nodedetects the environmental anomaly for the shipping container because thesize of the identified or otherwise sensed unresponsive group of the IDnodes in the unanticipated state of ceased broadcasting exceeds thethreshold setting. If not, method 3500 proceeds from step 3525 back tostep 3510. In a further embodiment of method 3500, the threshold settingmaintained by the command node that is used as part of step 3525 may beset by the command node, for example, depending on a combined count ofthe ID nodes monitored in the first set of the ID nodes and the secondset of the ID nodes; depending on a material characteristic of what iscontained in at least one of a plurality of packages disposed within theshipping container; and/or depending on a material characteristic ofwhat is contained in at least one of the packages disposed outside theshipping container but on the transit vehicle having custody of theshipping container.

For example, in an embodiment of method 3500, command node 24160 mayhave identified ID nodes 24120 d and 24120 e within the first set ofmonitored ID nodes within the shipping container 24300 a as well as IDnodes 24120 f and 24120 g within the second set of monitored ID nodesexternal to shipping container 24300 a as anticipated to be broadcastingbut now being in an unanticipated state of ceased broadcasting. If thethreshold setting maintained in memory of command node 24160 is three,then method 3500 would have command node 24160 determining in step 3525that the four identified ID nodes in the group in the unanticipatedstate of ceased broadcasting exceeds the threshold setting. Thus,command node 24160 may detect the environmental anomaly for shippingcontainer 24300 a at step 3530 upon the basis of the monitoring,identifying, and decisions made by the command node in steps 3510-3525.

At step 3535, method 3500 proceeds with the command node automaticallygenerating an alert notification about the detected environmentalanomaly for the shipping container, where the alert notification has analert level setting based upon whether the unresponsive group of the IDnodes includes any from the first set of the ID nodes and whether theunresponsive group of the ID nodes includes any from the second set ofthe ID nodes. In one example, the alert level setting may be implementedby the command node an initial degree of alert when the unresponsivegroup of the ID nodes includes only ID nodes from the second set of theID nodes disposed outside the shipping container. As such, the generatedalert notification about the detected environmental anomaly having theinitial degree of alert may be generated as an automatic warning about apotential fire outside of the shipping container and/or an automaticwarning about a potential fire within the shipping container.

In another example, the alert level setting may be implemented by thecommand node as an enhanced degree of alert when the unresponsive groupof the ID nodes includes only ID nodes from the first set of the IDnodes disposed within the shipping container. As such, the generatedalert notification about the detected environmental anomaly having theenhanced degree of alert may be generated as an automatic warning abouta fire inside of the shipping container as the enhanced degree of alertreflects a higher confidence level that the detected environmentalanomaly is the fire inside of the shipping container.

In still another example, the alert level setting may be implemented bythe command node as a high degree of alert when the unresponsive groupof the ID nodes includes ID nodes from both the first set of the IDnodes disposed within the shipping container and the second set of theID nodes disposed outside the shipping container. As such, the generatedalert notification about the detected environmental anomaly having thehigh degree of alert may be generated as an automatic warning about anexplosion involving contents of the shipping container, the high degreeof alert reflecting a higher confidence level that the detectedenvironmental anomaly involves at least a spreading fire inside of theshipping container.

At step 3540, method 3500 then proceeds to have the command nodetransmitting the alert notification to the transceiver unit (e.g.,external transceiver 24150) to initiate a mediation response related tothe detected environmental anomaly.

In further embodiments, method 3500 may include further steps to refineand update for known movement of ID nodes outside of the shippingcontainer. In more detail, a further embodiment of method 3500 may alsoinclude having the command node first requesting context data related tothe ID nodes from the second set of the ID nodes that are in theunresponsive group of the ID nodes (e.g., requesting such context datafrom onboard storage memory in the command node, from the externaltransceiver, or from a remote server in communication with the externaltransceiver). This requested context data (e.g., context data 26560)provides information on an anticipated location of the ID nodes from thesecond set of the ID nodes (those outside the shipping container) thatare in the unresponsive group of the ID nodes. The further embodiment ofmethod 3500 then has the command node predicting movement of any of theID nodes from the second set of the ID nodes that are in theunresponsive group of the ID nodes where the prediction operation isbased upon whether the anticipated location of any of the ID nodes fromthe second set of the ID nodes within the unresponsive group of the IDnodes is beyond a reception range for the command node as disposedrelative to the shipping container. The command node may then update theunresponsive group of the ID nodes to remove any of the ID nodes fromthe second set of the ID nodes that are (a) initially detected to bewithin the unresponsive group of the ID nodes and (b) that are predictedas moved beyond the reception range for the command node based upon therequested context data. The command node then may re-identify theenvironmental anomaly when the size of the updated unresponsive group ofthe ID nodes in the unanticipated state of ceased broadcasting exceedsthe threshold setting maintained by the command node, and then mayautomatically generate a refined alert notification about the detectedenvironmental anomaly for the shipping container. Such a refined alertnotification has a revised alert level setting based upon whether theupdated unresponsive group of the ID nodes includes any from the firstset of the ID nodes and whether the updated unresponsive group of the IDnodes includes any from the second set of the ID nodes. This furtherembodiment of method 3500 then may have the command node transmittingthe revised alert notification to the transceiver unit to initiate themediation response related to the detected environmental anomaly.

In another further embodiment of method 3500, the exemplary method mayinclude further steps to refine and update for known movement of theshipping container away from ID nodes external to the shippingcontainer. In more detail, such a further embodiment of method 3500 mayhave the command node requesting context data related to the ID nodesfrom the second set of the ID nodes that are in the unresponsive groupof the ID nodes and context data about the shipping container (e.g.,requesting such context data from onboard storage memory in the commandnode, from the external transceiver, or from a remote server incommunication with the external transceiver). Such requested data (e.g.,context data 26560 and location data 455) provides information on ananticipated location of the ID nodes from the second set of the ID nodesthat are in the unresponsive group of the ID nodes and an anticipatedlocation of the shipping container. The method may proceed withpredicting movement, by the command node, of the shipping container awayfrom any of the ID nodes from the second set of the ID nodes that are inthe unresponsive group of the ID nodes. Such predicted movement is basedupon whether the anticipated location of any of the ID nodes from thesecond set of the ID nodes within the unresponsive group of the ID nodesdiffers from the anticipated location of the shipping containeraccording to the requested context data. The method may then have thecommand node updating the unresponsive group of ID nodes to remove anyof the ID nodes from the second set of the ID nodes that are (a)initially detected to be within the unresponsive group of the ID nodesand (b) that are beyond a reception range for the command node given thepredicted movement of the shipping container away from any of the IDnodes from the second set of the ID nodes that are in the unresponsivegroup of the ID nodes. As part of this further embodiment of method3500, the command node may then re-identify the environmental anomalywhen the size of the updated unresponsive group of the ID nodes in theunanticipated state of ceased broadcasting exceeds the threshold settingmaintained by the command node, and then automatically generate arefined alert notification about the detected environmental anomaly forthe shipping container. The refined alert notification has a revisedalert level setting based upon whether the updated unresponsive group ofthe ID nodes includes any from the first set of the ID nodes and whetherthe updated unresponsive group of the ID nodes includes any from thesecond set of the ID nodes. The command node may then transmit therefined alert notification to the transceiver unit to initiate themediation response related to the detected environmental anomaly.

In still another further embodiment of method 3500, the alertnotification may identify a targeted mediation recipient. In moredetail, a more detailed embodiment may have step 3535 of method 3500automatically generating the alert notification, which identifies atargeted mediation recipient that is automatically selected by thecommand node based upon an extent of how much the size of theunresponsive group of ID nodes exceeds a threshold setting and basedupon the alert level setting. Such a targeted mediation recipient maycomprise, for example, an operator of the transit vehicle that can altermovement of the transit vehicle in response to the alert level settingand/or a logistics crew member of the transit vehicle that can inspectthe shipping container in response to the alert level setting.

The targeted mediation recipient, in another example, may be identifiedas a triggered fire suppression system (e.g., onboard fire suppressionsystem 25010) that is operative to automatically respond to the detectedenvironmental anomaly based upon receipt of the alert notification andbased upon the alert level setting. As such, an embodiment of method3500 may further include the step of automatically dispensing, by thefire suppression system, fire suppression agent into the shippingcontainer upon receipt of a trigger message from the externaltransceiver of the transit vehicle sent in response to the alertnotification. Such a trigger message from the external transceiver maybe generated in response to input to the external transceiver from alogistics crew member of the transit vehicle after inspecting theshipping container.

In yet another further embodiment of method 3500, a targeted mediationaction may be identified by the alert notification. In more detail,method 3500 may have the command node automatically generate the alertnotification, which identifies a targeted mediation action that isautomatically selected by the command node based upon an extent of howmuch the size of the unresponsive group of ID nodes exceeds a thresholdsetting and based upon the alert level setting. In even more detail, thecommand node may automatically select the targeted mediation actionbased upon, for example, how quickly members of the unresponsive groupof the ID nodes have changed broadcast behavior to become in theunanticipated state of ceased broadcasting; based upon a pattern ofchange as members of the unresponsive group of the ID nodes areinitially monitored and detected to have changed broadcast behavior tobecome in the unanticipated state of ceased broadcasting; or based uponwhere each member of the unresponsive group of the ID nodes is locatedrelative to the shipping container according to context data related tothe unresponsive group of the ID nodes.

The targeted mediation action identified by the command node may alsodepend upon further contextual information and may include, for example,an automatic response request for a triggered fire suppression system onthe transit vehicle, a request to change course of the transit vehiclefrom an existing travel path of the transit vehicle; and/or a request toinvestigate the shipping container. In more detail, a further embodimentof method 3500 may have the command node receiving vehicle status datafrom the external transceiver unit associated with the transit vehicle(e.g., external transceiver 24150). In such a situation, the targetedmediation action identified in the automatically generated alertnotification may depend upon a state of the transit vehicle as indicatedby the vehicle status data and depends upon the alert level setting.Such a state of the transit vehicle may, for example, include a takeoffvehicular status, a cruising vehicle status, a landing vehicular status,and a stationary vehicular status. Thus, when an aircraft is stationary,the vehicle status data provides relevant input, along with the alertlevel setting, on what the command node may identify as the targetedmediation action. This may be different if the aircraft is taking off,which may have the targeted mediation action being an automatic promptto abort the landing given the alert level setting so that logisticspersonnel may inspect the shipping container.

Similarly, the targeted mediation action identified in the automaticallygenerated alert notification may depend upon the status of the shippingcontainer or location data on the current location of the shippingcontainer. Thus, a further embodiment of method 3500 may have thecommand node accessing container status data maintained by the commandnode and associated with the shipping container. In such a situation,the targeted mediation action identified by the command node in theautomatically generated alert notification may depend upon a state ofthe shipping container as indicated in the container status data anddepends upon the alert level setting. Likewise, another embodiment ofmethod 3500 may have the command node detecting geolocation data relatedto a current location of the shipping container, so that the targetedmediation action identified by the command node in the automaticallygenerated alert notification may depend upon the current location of theshipping container as indicated in the geolocation data and depends uponthe alert level setting.

A further embodiment of method 3500 may have the communication profilemaintained on the command node for each of the ID nodes in the first andsecond set of ID nodes identifying a programmatic setting for abroadcast timing parameter that defines when a respective ID node isprogrammed to transmit an advertising message in the future. In thisway, the command node may use such information when determining when therespective ID node may be anticipated to be broadcasting. As such, themonitoring step 3510 in method 3500 may have the command node monitoringfor a shift in broadcast behavior of any of the ID nodes within thefirst set of the ID nodes and within the second set of the ID nodes awayfrom an anticipated broadcast behavior according to the communicationprofile maintained on the command node for each of the ID nodes in thefirst set of the ID nodes and the second set of the ID nodes.

Additionally, method 3500 may also leverage such communication profileinformation by further instructing each of the responsive ID nodes(i.e., those ID nodes not in the unresponsive group of the ID nodes butanticipated to be broadcasting) to broadcast at an altered messagingrate different from an initial messaging rate after initiallyidentifying the environmental anomaly so that each of the remaining IDnodes within the first set of the ID nodes and the second set of the IDnodes that are responsive and not included as a member of theunresponsive group of the ID nodes are operative to broadcast using thealtered messaging rate compared to prior to when the unresponsive groupof the ID nodes was initially identified. This further ability of thecommand node, as part of method 3500, to set and adjust how quickly theID nodes are broadcasting enables a level of adjustable data qualityrate changes that further enhances detecting and monitoring for anenvironmental anomaly associated with a shipping container near such IDnodes and related to the command node.

In more detail, method 3500 may have the command node instructing eachof the responsive ID nodes (i.e., those ID nodes not in the unresponsivegroup of the ID nodes but anticipated to be broadcasting) to broadcastat a second messaging rate that exceeds an initial messaging rate afterthe command node detects the environmental anomaly so that each of theID nodes within the first set of the ID nodes and the second set of theID nodes but not included as a member of the unresponsive group of theID nodes more frequently broadcasts compared to prior to when theunresponsive group of the ID nodes was detected. In a further example,the initial messaging rate may be set as an initial value correlated toan environmental risk associated with at least one of the packages—e.g.,one or more packages disposed within the shipping container, one or morepackages disposed outside the shipping container but within the transitvehicle having custody of the shipping container, or a combination ofpackages within the shipping container and disposed outside the shippingcontainer. Further still, an embodiment may have the second messagingrate for the ID nodes not in the unresponsive group of the ID nodesbeing set at a predetermined higher messaging rate based upon a type ofmaterial existing within at least one of a plurality of packagesdisposed within the shipping container.

A further embodiment of method 3500 may also involve confirming thevalidity of node communications being monitored so that the command nodedetections of and responses to an environmental anomaly may be morerobust and secure. For example, an embodiment of method 3500 mayimplement the monitoring step 3510 by having the command node (a)receiving a communication broadcasted from a first of the ID nodeswithin the first set of the ID nodes; (b) confirming, by the commandnode, the validity of the received communication; (c) repeating steps(a) and (b), by the command node, for the remainder of thecommunications received from any of the remaining ones of the ID nodeswithin the first set of the ID nodes; (d) receiving, by the commandnode, a communication broadcasted from a first of the ID nodes withinthe second set of the ID nodes; (e) confirming, by the command node, thevalidity of the received communication; and (f) repeating steps (d) and(e), by the command node, for the remainder of the communicationsreceived from any of the remaining ones of the ID nodes within thesecond set of the ID nodes. As such, detecting the unresponsive group ofthe ID nodes may then be based upon the monitoring step for the firstset of the ID nodes and upon the monitoring step for the second set ofthe ID nodes and based upon steps (a)-(f).

Confirming the validity in steps (b) and (e) above may be accomplishedin an “active” or “passive” validation process. For example, confirmingthe validity of the received communication in step (b) may be activelyaccomplished by having the command node (b1) actively sending anauthentication request to the first of the ID nodes within the first setof the ID nodes; and (b2) receiving, by the command node, a validationresponse from the first of the ID nodes within the first set of the IDnodes that authenticates the communication broadcasted from the first ofthe ID nodes within the first set of the ID nodes. In like manner,confirming the validity of the received communication in step (e) may beactively accomplished by having the command node (e1) actively sendingan authentication request to the first of the ID nodes within the secondset of the ID nodes; and (e2) receiving, by the command node, avalidation response from the first of the ID nodes within the second setof the ID nodes that authenticates the communication broadcasted fromthe first of the ID nodes within the second set of the ID nodes.

In a “passive” example, confirming the validity of the receivedcommunication in step (b) may be accomplished by having the command node(b1) accessing a validation sequence for the first of the ID nodeswithin the first set of the ID nodes, where the validation sequence ismaintained by the command node and characterizes expected broadcastsfrom the first of the ID nodes within the first set of the ID nodes; and(b2) determining if the received communication from the first of the IDnodes within the first set of the ID nodes matches a predetermined oneof the expected broadcasts from the first of the ID nodes within thefirst set of the ID nodes according to the validation sequence storedwithin the command node. The predetermined one of the expectedbroadcasts may be a rotating value previously received by the commandnode for the first of the ID nodes within the first set of the ID nodes.In like manner, confirming the validity of the received communication instep (e) may be accomplished by having the command node (e1) accessing avalidation sequence for the first of the ID nodes within the second setof the ID nodes, where the validation sequence is maintained by thecommand node and characterizes expected broadcasts from the first of theID nodes within the second set of the ID nodes; and (e2) determining ifthe received communication from the first of the ID nodes within thesecond set of the ID nodes matches a predetermined one of the expectedbroadcasts from the first of the ID nodes within the second set of theID nodes according to the validation sequence stored within the commandnode. And likewise, the predetermined one of the expected broadcasts maybe a rotating value previously received by the command node for thefirst of the ID nodes within the second set of the ID nodes.

Additional embodiments of method 3500 may involve ID nodes that areparticularly disposed and configured relative to the shipping containerand the packages on the transit vehicle. For example, each of the IDnodes being monitored may be associated with a respective one of theplurality of packages on the transit vehicle (e.g., as shown in FIG.31). As such, the ID nodes may travel with their respective package, beaffixed to the outside of one of the packages, and/or be integrated aspart of one of the packages.

In another example, the ID nodes being monitored as part of method 3500may involve combinations of ID nodes and packages inside and outside ofthe shipping container. In more detail, an embodiment of method 3500 mayhave the first set of the ID nodes monitored by the command node beingmade up of a first group of ID nodes and a second group of ID nodes,where the first group of ID nodes is associated with a first group ofthe packages being disposed within the shipping container and where thesecond group of the ID nodes is not associated with any of the packagesbeing disposed within the shipping container. The second set of the IDnodes monitored by the command node may be made up of a third group ofID nodes and a fourth group of ID nodes, where the third group of IDnodes is associated with a third group of the packages being disposedoutside the shipping container and where the fourth group of the IDnodes is not associated with any of the packages being disposed outsidethe shipping container and on the transit vehicle.

In still another example, the ID nodes monitored within the shippingcontainer may be package ID nodes, while the ID nodes monitored outsidethe shipping container may be a combination of package ID nodes andnon-package ID nodes. In more detail, an embodiment of method 3500 mayhave the first set of the ID nodes monitored by the command node beingassociated with a first group of the packages being disposed within theshipping container; and the second set of the ID nodes monitored by thecommand node may be made up of a third group of ID nodes and a fourthgroup of ID nodes, where the third group of ID nodes is associated witha third group of the packages being disposed outside the shippingcontainer and where the fourth group of the ID nodes is not associatedwith any of the packages being disposed outside the shipping containerand on the transit vehicle.

In yet another example, the ID nodes monitored within the shippingcontainer may be non-package ID nodes, while the ID nodes monitoredoutside the shipping container may be a combination of package ID nodesand non-package ID nodes. In more detail, an embodiment of method 3500may have the first set of the ID nodes monitored by the command nodebeing not associated with any of the packages being disposed within theshipping container; and the second set of the ID nodes monitored by thecommand node may be made up of a third group of ID nodes and a fourthgroup of ID nodes, where the third group of ID nodes is associated witha third group of the packages being disposed outside the shippingcontainer and where the fourth group of the ID nodes is not associatedwith any of the packages being disposed outside the shipping containerand on the transit vehicle.

Another exemplary embodiment of method 3500 may have the ID nodesmonitored within the shipping container being a combination of packageand non-package ID nodes, while the ID nodes monitored outside theshipping container being package ID nodes. In more detail, such anembodiment of method 3500 may have the first set of the ID nodesmonitored by the command node being made up of a first group of ID nodesand a second group of ID nodes, where the first group of ID nodes isassociated with a first group of the packages being disposed within theshipping container and where the second group of the ID nodes is notassociated with any of the packages being disposed within the shippingcontainer; and where the second set of the ID nodes monitored by thecommand node being associated with a third group of the packages beingdisposed outside the shipping container and on the transit vehicle.

Further still, another embodiment of method 3500 may have the ID nodesmonitored within the shipping container being a combination of packageand non-package ID nodes, while the ID nodes monitored outside theshipping container being non-package ID nodes. In more detail, such anembodiment of method 3500 may have the first set of the ID nodesmonitored by the command node being made up of a first group of ID nodesand a second group of ID nodes, where the first group of ID nodes isassociated with a first group of the packages being disposed within theshipping container and where the second group of the ID nodes is notassociated with any of the packages being disposed within the shippingcontainer; and where the second set of the ID nodes monitored by thecommand node being not associated with any of the packages beingdisposed outside the shipping container and on the transit vehicle.

Those skilled in the art will appreciate that exemplary method 3500 asdisclosed and explained above in various embodiments may be implementedusing an exemplary improved monitoring system for detecting anenvironmental anomaly in a shipping container. Such a system mayinclude, for example, a command node that interactively monitors IDnodes disposed within and external to the shipping container and reportsan alert notification related to the environmental anomaly to causedifferent types of mediation responses such as that explained above withreference to FIGS. 31-34 and its exemplary elements. In more detail,such an embodiment of an improved monitoring system, as explained aboverelative to operations according to method 3500 and with elements fromFIGS. 31-34, uses at least ID nodes disposed within and external to theshipping container (e.g., ID nodes 24120 a-24120 i as they appear in theexemplary configurations shown in FIGS. 31, 33, and 34) running one ormore ID node monitoring program code as part of node control andmanagement code 325 to control operations of the ID nodes to generateand broadcast wireless communications, as well as a command node mountedto the shipping container (e.g., command node 24160 in FIGS. 31, 33, and34) running one or more parts of CN control & management code 26425 tocontrol the operations of the command node as part of monitoring for anddetecting an environmental anomaly using ID nodes anticipated to bebroadcasting within and external to the shipping container as well asgenerating the alert notification and transmitting that notification tothe external transceiver unit to initiate a type of mediation response(such as triggering onboard fire suppression system 25010). Such codemay be stored on a non-transitory computer-readable medium, such asmemory storage 26415 on command node 24160 (an embodiment of exemplarycommand node 26000) and memory storage 315 on ID nodes 24120 a-24120 i(embodiments of exemplary ID node 120 a). Thus, when executing suchcode, the ID nodes and the command node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 3500 and variations of that method. Further systemembodiments may also include the onboard fire suppression system as acomponent that is caused to expel fire suppression agent into thecommand node's shipping container in response to the alert notification(directly) or in response to an activation control signal from theexternal transceiver generated as a result of the external transceiverreceiving the alert notification from the command node.

Further method and system embodiments may provide further detail onsituations where the command node itself may operate as a type oftransceiver to directly cause initiation of a mediation response fromthe onboard fire suppression system. As described above relative toFIGS. 32A-32C, exemplary fire suppression system 25010 may be activateddirectly by the command node 24160 of a shipping container 24300 a orindirectly by the command node 24160 via the alert notification sent tothe external transceiver 24150, which then sends an activation controlsignal to exemplary fire suppression system 25010. Thus, embodiments mayhave command node 24160 programmed to send the alert notificationdirectly to onboard systems (such as a display in a cockpit or logisticssupport area of a transit vehicle 24200, or an onboard fire suppressionsystem on the transit vehicle 24200) without needing to involve anintermediary separate external transceiver (e.g., external transceiver24150). Further embodiments may deploy a built-in communicationinterface as part of other transit vehicle electronics (e.g., a cockpitdisposed transceiver) that may operate as a type of external transceiverwith which to communicate with the command node 24160 of a particularshipping container 24300. Additional embodiments may also implementtransceiver 24150 as being internal to the shipping container or mayhave the command node and internal transceiver that initiates themediation responsive action being the same node-based transceiver device(i.e., the command node 24160 operates as the external transceiver andgenerates the alert notification to directly initiate the mediationresponsive action).

Additional method and system embodiments may have the shippingcontainer's command node more particularly and selectively transmit thealert notification to different targeted mediation recipients based onthe alert level setting (e.g., to the external transceiver when thealert level setting is at a predetermined alert level to initiate afirst mediation response related to the detected environmental anomaly,and to the onboard fire suppression system on the transit vehicle whenthe alert level setting is above the predetermined alert level todirectly cause the onboard fire suppression system to automaticallydispense a fire suppressant agent within the shipping container as asecond mediation response related to the detected environmental anomaly.In these embodiments, this type of automatic selective mediationresponse may further enhance the contextual rapid response to anydetected environmental anomaly with the shipping container.

FIG. 36 is a flow diagram illustrating an exemplary method formonitoring for an environmental anomaly related to a shipping containerusing a wireless node network having at least a command node associatedwith the shipping container, ID nodes within the shipping container andoutside the shipping container, and an onboard fire suppression systemand external transceiver in accordance with an embodiment of theinvention.

In particular, FIG. 36 describes an exemplary improved method 3600 formonitoring for an environmental anomaly related to a shipping container(e.g., shipping container 24300 a) using a wireless node network. Theshipping container involved in method 3600 is being transported on atransit vehicle (e.g., transit vehicle 24200—such as an aircraft,railway conveyance, a maritime vessel, or a roadway conveyance) thatalso transports multiple packages (e.g., packages 24400 a-24400 h asshown in FIG. 31). The wireless node network involved in method 3600 hasat least a plurality of ID nodes (e.g., ID node 24120 a-24120 h as shownin FIG. 31), a command node associated with the shipping container(e.g., command node 241260 associated with and mounted to shippingcontainer 24300 a), and an onboard fire suppression system for theshipping container (e.g., fire suppression system 25010). The commandnode used as part of method 3600 may, for example, be implemented as acontainer node integrated as part of the shipping container or aself-locating master node implemented separately from the shippingcontainer. The ID nodes used as part of method 3600 include a first setof the ID nodes disposed within the shipping container (e.g., ID nodes24120 c-24120 e) and a second set of the ID nodes disposed outside theshipping container (e.g., ID nodes 24120 a, 24120 b, and 24120 f-24120h). In this configuration, the command node involved in method 3600 isoperative to communicate with each of the ID nodes in the first set ofthe ID nodes and the second ID nodes, the onboard fire suppressionsystem, and an external transceiver unit associated with the transitvehicle (e.g., external transceiver 24150 on transit vehicle 24200).Notably, the embodiment of method 3600 is similar to method 3500 withthe exception of the responsive actions taken by the command node whengenerating and transmitting the alert notification.

In more detail and referring now to FIG. 36, exemplary method 3600begins at step 3605 with the command node determining which of the IDnodes disposed in and near the shipping container are anticipated to bebroadcasting according to a communication profile on what ID nodes arewithin and located near the shipping container. For example, commandnode 24160 may reference profile data 430 (as well as location dataand/or association data) that may indicate what ID nodes are withinshipping container 24300 a or loaded within transit vehicle storage24205. Using this information, command node 24160 may initiatecommunication with any ID nodes within the command node's transmissionand reception range (e.g., what ID nodes may receive communications fromcommand node 24160 and which ID nodes respond to such communicationsfrom the command node 24160). Those ID nodes that may establish initialcommunications with command node 24160—i.e., ID nodes within shippingcontainer 24300 a and outside of 24300 a—may be identified as potentialID nodes to be monitored as part of the embodiment of method 3600 aslong as the communication profile information on each of those potentialID nodes indicates the particular ID node is anticipated to bebroadcasting so that the command node 24160 is able to count oncommunications from those ID nodes anticipated to be broadcasting undernormal conditions.

At step 3610, method 3600 continues with the command node monitoring foran unanticipated state of ceased broadcasting from any of the ID nodeswithin the first set of the ID nodes disposed within the shippingcontainer according to a communication profile for each the ID nodes inthe first set of the ID nodes maintained on the command node, as well asmonitoring for an unanticipated state of ceased broadcasting from any ofthe ID nodes within the second set of the ID nodes disposed outside theshipping container according to a communication profile for each the IDnodes in the second set of the ID nodes. For example, command node 24160shown in FIG. 31 may monitor the first set of ID nodes (e.g., ID nodes24120 c-24120 e disposed within shipping container 24300 a) as well asmonitor the second set of ID nodes (e.g., ID nodes 24120 a, 24120 b, and24120 f-24120 h disposed outside shipping container 24300 a). Commandnode 24160 would be monitoring those ID nodes in particular as part ofstep 3510 because the communication profile data on each of those nodes(as indicated in profile data 430 on command node 24160) indicates theyare anticipated to be broadcasting.

At step 3615, method 3600 continues by identifying one or more ID nodesfrom the first set and/or second set of the monitored ID nodes as beingunresponsive or in an unanticipated state of ceased broadcasting. Inmore detail, this may have the command node detecting an unresponsivegroup of the ID nodes to be in the unanticipated state of ceasedbroadcasting based upon the monitoring step for the first set of the IDnodes and upon the monitoring step for the second set of the ID nodes.The command node, such as command node 24160, may then determine if theunresponsive group of the ID nodes includes any from the first set ofthe ID nodes (i.e., those monitored ID nodes disposed within theshipping container) and if the unresponsive group of the ID nodesincludes any from the second set of the ID nodes (i.e., those monitoredID nodes disposed external to the shipping container).

At step 3620, method 3600 continues with the command node adding any ofthe identified ID nodes from step 3615 to a group of ID nodes in theunanticipated state of ceased broadcasting. Then, at decision step 3625,method 3600 has the command node determining if the size of the group ofID nodes in the unanticipated state of ceased broadcasting exceeds athreshold setting maintained by the command node. If so, method 3600proceeds from step 3625 directly to step 3630 where the command nodedetects the environmental anomaly for the shipping container because thesize of the identified or otherwise sensed unresponsive group of the IDnodes in the unanticipated state of ceased broadcasting exceeds thethreshold setting. If not, method 3600 proceeds from step 3625 back tostep 3610. In a further embodiment of method 3600, the threshold settingmaintained by the command node that is used as part of step 3625 may beset by the command node, for example, depending on a combined count ofthe ID nodes monitored in the first set of the ID nodes and the secondset of the ID nodes; depending on a material characteristic of what iscontained in at least one of a plurality of packages disposed within theshipping container; and/or depending on a material characteristic ofwhat is contained in at least one of the packages disposed outside theshipping container but on the transit vehicle having custody of theshipping container.

At step 3635, method 3600 proceeds with the command node automaticallygenerating an alert notification about the detected environmentalanomaly for the shipping container, where the alert notification has analert level setting based upon whether the unresponsive group of the IDnodes includes any from the first set of the ID nodes and whether theunresponsive group of the ID nodes includes any from the second set ofthe ID nodes. In one example, the alert level setting may be implementedby the command node an initial degree of alert when the unresponsivegroup of the ID nodes includes only ID nodes from the second set of theID nodes disposed outside the shipping container. As such, the generatedalert notification about the detected environmental anomaly having theinitial degree of alert may be generated as an automatic warning about apotential fire outside of the shipping container and/or an automaticwarning about a potential fire within the shipping container.

In another example, the alert level setting may be implemented by thecommand node as an enhanced degree of alert when the unresponsive groupof the ID nodes includes only ID nodes from the first set of the IDnodes disposed within the shipping container. As such, the generatedalert notification about the detected environmental anomaly having theenhanced degree of alert may be generated as an automatic warning abouta fire inside of the shipping container as the enhanced degree of alertreflects a higher confidence level that the detected environmentalanomaly is the fire inside of the shipping container.

In still another example, the alert level setting may be implemented bythe command node as a high degree of alert when the unresponsive groupof the ID nodes includes ID nodes from both the first set of the IDnodes disposed within the shipping container and the second set of theID nodes disposed outside the shipping container. As such, the generatedalert notification about the detected environmental anomaly having thehigh degree of alert may be generated as an automatic warning about anexplosion involving contents of the shipping container, the high degreeof alert reflecting a higher confidence level that the detectedenvironmental anomaly involves at least a spreading fire inside of theshipping container.

At steps 3640-3650, exemplary method 3600 differs from method 3500described above in how the command node functions to respond to thedetected environmental anomaly relative to initiating different kinds ofmediation responses based upon the alert level setting. In particular,method 3600 proceeds to decision step 3640 where the command nodedetermines if the alert level setting exceeds a predetermined alertlevel (such as the initial degree of alert described above). If not,step 3640 proceeds to step 3645 where the command node transmits thealert notification to the external transceiver on the transit vehicle toinitiate a first mediation response related to the detectedenvironmental anomaly before method 3600 returns to step 3610 forcontinued monitoring for unresponsive ID nodes anticipated to bebroadcasting. But if so, step 3640 proceeds directly to step 3650 wherethe command node transmits the alert notification directly to theonboard fire suppression system on the transit vehicle (given the alertlevel setting is above the predetermined alert level) to directly causethe onboard fire suppression system to automatically dispense a firesuppressant agent within the shipping container as a second mediationresponse related to the detected environmental anomaly. This type ofoperation of method 3600 allows for a tiered approach that has thecommand node being configured and operative to provide direct andimmediate responsive initiation of the onboard fire suppression system(rather than relying on a relayed message through the externaltransceiver on the transit vehicle) under certain alert level settings(based on how the environmental anomaly is detected and what ID nodeshave become unresponsive within and external to the shipping container).

In further embodiments, method 3600 may include further steps to refineand update for known movement of ID nodes outside of the shippingcontainer. In more detail, a further embodiment of method 3600 may alsoinclude having the command node first requesting context data related tothe ID nodes from the second set of the ID nodes that are in theunresponsive group of the ID nodes (e.g., requesting such context datafrom onboard storage memory in the command node, from the externaltransceiver, or from a remote server in communication with the externaltransceiver). This requested context data (e.g., context data 26560)provides information on an anticipated location of the ID nodes from thesecond set of the ID nodes (those outside the shipping container) thatare in the unresponsive group of the ID nodes. The further embodiment ofmethod 3600 then has the command node predicting movement of any of theID nodes from the second set of the ID nodes that are in theunresponsive group of the ID nodes where the prediction operation isbased upon whether the anticipated location of any of the ID nodes fromthe second set of the ID nodes within the unresponsive group of the IDnodes is beyond a reception range for the command node as disposedrelative to the shipping container. The command node may then update theunresponsive group of the ID nodes to remove any of the ID nodes fromthe second set of the ID nodes that are (a) initially detected to bewithin the unresponsive group of the ID nodes and (b) that are predictedas moved beyond the reception range for the command node based upon therequested context data. The command node then may re-identify theenvironmental anomaly when the size of the updated unresponsive group ofthe ID nodes in the unanticipated state of ceased broadcasting exceedsthe threshold setting maintained by the command node, and then mayautomatically generate a refined alert notification about the detectedenvironmental anomaly for the shipping container. Such a refined alertnotification has a revised alert level setting based upon whether theupdated unresponsive group of the ID nodes includes any from the firstset of the ID nodes and whether the updated unresponsive group of the IDnodes includes any from the second set of the ID nodes. This furtherembodiment of method 3600 then may have the command node transmittingthe refined alert notification to the external transceiver on thetransit vehicle when the alert level setting is at the predeterminedalert level to initiate a third mediation response related to thedetected environmental anomaly (e.g., a mediation response to cause theexternal transceiver to generate a warning for an operator of thetransit vehicle based upon the refined alert notification), andtransmitting the refined alert notification directly to the onboard firesuppression system on the transit vehicle when the alert level settingis above the predetermined alert level to directly cause the onboardfire suppression system to continue to dispense the fire suppressantagent within the shipping container as part of the second mediationresponse related to the detected environmental anomaly.

In another further embodiment of method 3600, the exemplary method mayinclude further steps to refine and update for known movement of theshipping container away from ID nodes external to the shippingcontainer. In more detail, such a further embodiment of method 3600 mayhave the command node requesting context data related to the ID nodesfrom the second set of the ID nodes that are in the unresponsive groupof the ID nodes and context data about the shipping container (e.g.,requesting such context data from onboard storage memory in the commandnode, from the external transceiver, or from a remote server incommunication with the external transceiver). Such requested data (e.g.,context data 26560 and location data 455) provides information on ananticipated location of the ID nodes from the second set of the ID nodesthat are in the unresponsive group of the ID nodes and an anticipatedlocation of the shipping container. The method may proceed withpredicting movement, by the command node, of the shipping container awayfrom any of the ID nodes from the second set of the ID nodes that are inthe unresponsive group of the ID nodes. Such predicted movement is basedupon whether the anticipated location of any of the ID nodes from thesecond set of the ID nodes within the unresponsive group of the ID nodesdiffers from the anticipated location of the shipping containeraccording to the requested context data. The method may then have thecommand node updating the unresponsive group of ID nodes to remove anyof the ID nodes from the second set of the ID nodes that are (a)initially detected to be within the unresponsive group of the ID nodesand (b) that are beyond a reception range for the command node given thepredicted movement of the shipping container away from any of the IDnodes from the second set of the ID nodes that are in the unresponsivegroup of the ID nodes. As part of this further embodiment of method3600, the command node may then re-identify the environmental anomalywhen the size of the updated unresponsive group of the ID nodes in theunanticipated state of ceased broadcasting exceeds the threshold settingmaintained by the command node, and then automatically generate arefined alert notification about the detected environmental anomaly forthe shipping container. The refined alert notification has a revisedalert level setting based upon whether the updated unresponsive group ofthe ID nodes includes any from the first set of the ID nodes and whetherthe updated unresponsive group of the ID nodes includes any from thesecond set of the ID nodes. The command node may then transmit therefined alert notification to the external transceiver on the transitvehicle based when the alert level setting is at the predetermined alertlevel to initiate a third mediation response related to the detectedenvironmental anomaly (e.g., a mediation response that causes theexternal transceiver to generate a warning for an operator of thetransit vehicle based upon the refined alert notification on a displaycoupled to or integrated as part of the external transceiver), andtransmit the refined alert notification directly to the onboard firesuppression system on the transit vehicle when the alert level settingis above the predetermined alert level to directly cause the onboardfire suppression system to continue to dispense the fire suppressantagent within the shipping container as part of the second mediationresponse related to the detected environmental anomaly.

In still another further embodiment of method 3600, the alertnotification may identify a targeted mediation recipient. In moredetail, a more detailed embodiment may have step 3635 of method 3500automatically generating the alert notification, which identifies atargeted mediation recipient that is automatically selected by thecommand node based upon an extent of how much the size of theunresponsive group of ID nodes exceeds a threshold setting and basedupon the alert level setting. Such a targeted mediation recipient maycomprise, for example, an operator of the transit vehicle that can altermovement of the transit vehicle in response to the alert level settingand/or a logistics crew member of the transit vehicle that can inspectthe shipping container in response to the alert level setting. Thus, thefirst mediation response initiated in step 3645 may be responsivelycausing the external transceiver to prompt the operator of the transitvehicle to alter movement of the transit vehicle in response to thealert level setting or responsively causing the external transceiver toprompt the logistics crew member of the transit vehicle to inspect theshipping container in response to the alert level setting.

In more detail, step 3635 of method 3600 may be implemented by havingthe command node's automatically generated alert notificationidentifying the first mediation response based upon an extent of howmuch the size of the unresponsive group of ID nodes exceeds thethreshold setting and based upon the alert level setting. In thissituation, the first mediation response may be automatically selected bythe command node based upon, for example, how quickly members of theunresponsive group of the ID nodes have changed broadcast behavior tobecome in the unanticipated state of ceased broadcasting; based upon apattern of change as members of the unresponsive group of the ID nodesare initially monitored and detected to have changed broadcast behaviorto become in the unanticipated state of ceased broadcasting; and/orbased upon where each member of the unresponsive group of the ID nodesis located relative to the shipping container according to context datarelated to the unresponsive group of the ID nodes.

The targeted mediation action identified by the command node may alsodepend upon further contextual information. In more detail, a furtherembodiment of method 3500 may have the command node receiving vehiclestatus data from the external transceiver unit associated with thetransit vehicle (e.g., external transceiver 24150). In such a situation,the first mediation response in step 3645 may depend upon a state of thetransit vehicle as indicated by the vehicle status data and depends uponthe alert level setting. Such a state of the transit vehicle may, forexample, include a takeoff vehicular status, a cruising vehicle status,a landing vehicular status, and a stationary vehicular status. Thus,when an aircraft is stationary, the vehicle status data providesrelevant input, along with the alert level setting, on what the commandnode may identify as the targeted mediation action. This may bedifferent if the aircraft is taking off, which may have the targetedmediation action being an automatic prompt to abort the landing giventhe alert level setting so that logistics personnel may inspect theshipping container.

Similarly, the first mediation response may depend upon the status ofthe shipping container or location data on the current location of theshipping container. Thus, a further embodiment of method 3600 may havethe command node accessing container status data maintained by thecommand node and associated with the shipping container. In such asituation, the first mediation response may depend upon a state of theshipping container as indicated in the container status data and dependsupon the alert level setting. Likewise, another embodiment of method3600 may have the command node detecting geolocation data related to acurrent location of the shipping container, so that the first mediationresponse depends upon the current location of the shipping container asindicated in the geolocation data and depends upon the alert levelsetting.

A further embodiment of method 3600 may have the communication profilemaintained on the command node for each of the ID nodes in the first andsecond set of ID nodes identifying a programmatic setting for abroadcast timing parameter that defines when a respective ID node isprogrammed to transmit an advertising message in the future. In thisway, the command node may use such information when determining when therespective ID node may be anticipated to be broadcasting. As such, themonitoring step 3610 in method 3600 may have the command node monitoringfor a shift in broadcast behavior of any of the ID nodes within thefirst set of the ID nodes and within the second set of the ID nodes awayfrom an anticipated broadcast behavior according to the communicationprofile maintained on the command node for each of the ID nodes in thefirst set of the ID nodes and the second set of the ID nodes.

Additionally, method 3600 may also leverage such communication profileinformation by further instructing each of the responsive ID nodes(i.e., those ID nodes not in the unresponsive group of the ID nodes butanticipated to be broadcasting) to broadcast at an altered messagingrate different from an initial messaging rate after initiallyidentifying the environmental anomaly so that each of the remaining IDnodes within the first set of the ID nodes and the second set of the IDnodes that are responsive and not included as a member of theunresponsive group of the ID nodes are operative to broadcast using thealtered messaging rate compared to prior to when the unresponsive groupof the ID nodes was initially identified. This further ability of thecommand node, as part of method 3500, to set and adjust how quickly theID nodes are broadcasting enables a level of adjustable data qualityrate changes that further enhances detecting and monitoring for anenvironmental anomaly associated with a shipping container near such IDnodes and related to the command node.

In more detail, method 3600 may have the command node instructing eachof the responsive ID nodes (i.e., those ID nodes not in the unresponsivegroup of the ID nodes but anticipated to be broadcasting) to broadcastat a second messaging rate that exceeds an initial messaging rate afterthe command node detects the environmental anomaly in step 3630 so thateach of the ID nodes within the first set of the ID nodes and the secondset of the ID nodes but not included as a member of the unresponsivegroup of the ID nodes more frequently broadcasts compared to prior towhen the unresponsive group of the ID nodes was detected. In a furtherexample, the initial messaging rate may be set as an initial valuecorrelated to an environmental risk associated with at least one of thepackages—e.g., one or more packages disposed within the shippingcontainer, one or more packages disposed outside the shipping containerbut within the transit vehicle having custody of the shipping container,or a combination of packages within the shipping container and disposedoutside the shipping container. Further still, an embodiment may havethe second messaging rate for the ID nodes not in the unresponsive groupof the ID nodes being set at a predetermined higher messaging rate basedupon a type of material existing within at least one of a plurality ofpackages disposed within the shipping container.

A further embodiment of method 3600 may also involve confirming thevalidity of node communications being monitored as part of step 3610 sothat the command node detections of and responses to an environmentalanomaly may be more robust and secure. For example, an embodiment ofmethod 3600 may implement the monitoring step 3610 by having the commandnode (a) receiving a communication broadcasted from a first of the IDnodes within the first set of the ID nodes; (b) confirming, by thecommand node, the validity of the received communication; (c) repeatingsteps (a) and (b), by the command node, for the remainder of thecommunications received from any of the remaining ones of the ID nodeswithin the first set of the ID nodes; (d) receiving, by the commandnode, a communication broadcasted from a first of the ID nodes withinthe second set of the ID nodes; (e) confirming, by the command node, thevalidity of the received communication; and (f) repeating steps (d) and(e), by the command node, for the remainder of the communicationsreceived from any of the remaining ones of the ID nodes within thesecond set of the ID nodes. As such, detecting the unresponsive group ofthe ID nodes may then be based upon the monitoring step for the firstset of the ID nodes and upon the monitoring step for the second set ofthe ID nodes and based upon steps (a)-(f).

Confirming the validity in steps (b) and (e) above may be accomplishedin an “active” or “passive” validation process. For example, confirmingthe validity of the received communication in step (b) may be activelyaccomplished by having the command node (b1) actively sending anauthentication request to the first of the ID nodes within the first setof the ID nodes; and (b2) receiving, by the command node, a validationresponse from the first of the ID nodes within the first set of the IDnodes that authenticates the communication broadcasted from the first ofthe ID nodes within the first set of the ID nodes. In like manner,confirming the validity of the received communication in step (e) may beactively accomplished by having the command node (e1) actively sendingan authentication request to the first of the ID nodes within the secondset of the ID nodes; and (e2) receiving, by the command node, avalidation response from the first of the ID nodes within the second setof the ID nodes that authenticates the communication broadcasted fromthe first of the ID nodes within the second set of the ID nodes.

In a “passive” example, confirming the validity of the receivedcommunication in step (b) may be accomplished by having the command node(b1) accessing a validation sequence for the first of the ID nodeswithin the first set of the ID nodes, where the validation sequence ismaintained by the command node and characterizes expected broadcastsfrom the first of the ID nodes within the first set of the ID nodes; and(b2) determining if the received communication from the first of the IDnodes within the first set of the ID nodes matches a predetermined oneof the expected broadcasts from the first of the ID nodes within thefirst set of the ID nodes according to the validation sequence storedwithin the command node. The predetermined one of the expectedbroadcasts may be a rotating value previously received by the commandnode for the first of the ID nodes within the first set of the ID nodes.In like manner, confirming the validity of the received communication instep (e) may be accomplished by having the command node (e1) accessing avalidation sequence for the first of the ID nodes within the second setof the ID nodes, where the validation sequence is maintained by thecommand node and characterizes expected broadcasts from the first of theID nodes within the second set of the ID nodes; and (e2) determining ifthe received communication from the first of the ID nodes within thesecond set of the ID nodes matches a predetermined one of the expectedbroadcasts from the first of the ID nodes within the second set of theID nodes according to the validation sequence stored within the commandnode. And likewise, the predetermined one of the expected broadcasts maybe a rotating value previously received by the command node for thefirst of the ID nodes within the second set of the ID nodes.

Like method 3500, additional embodiments of method 3600 may involve IDnodes that are particularly disposed and configured relative to theshipping container and the packages on the transit vehicle. For example,each of the ID nodes being monitored may be associated with a respectiveone of the plurality of packages on the transit vehicle (e.g., as shownin FIG. 31). As such, the ID nodes may travel with their respectivepackage, be affixed to the outside of one of the packages, and/or beintegrated as part of one of the packages.

In another example, the ID nodes being monitored as part of method 3500may involve combinations of ID nodes and packages inside and outside ofthe shipping container. In more detail, an embodiment of method 3600 mayhave the first set of the ID nodes monitored by the command node beingmade up of a first group of ID nodes and a second group of ID nodes,where the first group of ID nodes is associated with a first group ofthe packages being disposed within the shipping container and where thesecond group of the ID nodes is not associated with any of the packagesbeing disposed within the shipping container. The second set of the IDnodes monitored by the command node may be made up of a third group ofID nodes and a fourth group of ID nodes, where the third group of IDnodes is associated with a third group of the packages being disposedoutside the shipping container and where the fourth group of the IDnodes is not associated with any of the packages being disposed outsidethe shipping container and on the transit vehicle.

In still another example, the ID nodes monitored within the shippingcontainer may be package ID nodes, while the ID nodes monitored outsidethe shipping container may be a combination of package ID nodes andnon-package ID nodes. In more detail, an embodiment of method 3600 mayhave the first set of the ID nodes monitored by the command node beingassociated with a first group of the packages being disposed within theshipping container; and the second set of the ID nodes monitored by thecommand node may be made up of a third group of ID nodes and a fourthgroup of ID nodes, where the third group of ID nodes is associated witha third group of the packages being disposed outside the shippingcontainer and where the fourth group of the ID nodes is not associatedwith any of the packages being disposed outside the shipping containerand on the transit vehicle.

In yet another example, the ID nodes monitored within the shippingcontainer may be non-package ID nodes, while the ID nodes monitoredoutside the shipping container may be a combination of package ID nodesand non-package ID nodes. In more detail, an embodiment of method 3600may have the first set of the ID nodes monitored by the command nodebeing not associated with any of the packages being disposed within theshipping container; and the second set of the ID nodes monitored by thecommand node may be made up of a third group of ID nodes and a fourthgroup of ID nodes, where the third group of ID nodes is associated witha third group of the packages being disposed outside the shippingcontainer and where the fourth group of the ID nodes is not associatedwith any of the packages being disposed outside the shipping containerand on the transit vehicle.

Another exemplary embodiment of method 3600 may have the ID nodesmonitored within the shipping container being a combination of packageand non-package ID nodes, while the ID nodes monitored outside theshipping container being package ID nodes. In more detail, such anembodiment of method 3600 may have the first set of the ID nodesmonitored by the command node being made up of a first group of ID nodesand a second group of ID nodes, where the first group of ID nodes isassociated with a first group of the packages being disposed within theshipping container and where the second group of the ID nodes is notassociated with any of the packages being disposed within the shippingcontainer; and where the second set of the ID nodes monitored by thecommand node being associated with a third group of the packages beingdisposed outside the shipping container and on the transit vehicle.

Further still, another embodiment of method 3600 may have the ID nodesmonitored within the shipping container being a combination of packageand non-package ID nodes, while the ID nodes monitored outside theshipping container being non-package ID nodes. In more detail, such anembodiment of method 3600 may have the first set of the ID nodesmonitored by the command node being made up of a first group of ID nodesand a second group of ID nodes, where the first group of ID nodes isassociated with a first group of the packages being disposed within theshipping container and where the second group of the ID nodes is notassociated with any of the packages being disposed within the shippingcontainer; and where the second set of the ID nodes monitored by thecommand node being not associated with any of the packages beingdisposed outside the shipping container and on the transit vehicle.

Those skilled in the art will appreciate that exemplary method 3600 asdisclosed and explained above in various embodiments may be implementedusing an exemplary improved monitoring system for detecting anenvironmental anomaly in a shipping container. Such a system mayinclude, for example, at least a command node that interactivelymonitors ID nodes disposed within and external to the shipping containerand reports an alert notification related to the environmental anomalyto cause different types of mediation responses by an externaltransceiver on the transit vehicle and an onboard fire suppressionsystem as that explained above with reference to FIGS. 31-34 and itsexemplary elements. In more detail, such an embodiment of an improvedmonitoring system, as explained above relative to operations accordingto method 3600 and with elements from FIGS. 31-34, uses at least IDnodes disposed within and external to the shipping container (e.g., IDnodes 24120 a-24120 i as they appear in the exemplary configurationsshown in FIGS. 31, 33, and 34) running one or more ID node monitoringprogram code as part of node control and management code 325 to controloperations of the ID nodes to generate and broadcast wirelesscommunications, as well as a command node mounted to the shippingcontainer (e.g., command node 24160 in FIGS. 31, 33, and 34) running oneor more parts of CN control & management code 26425 to control theoperations of the command node as part of monitoring for and detectingan environmental anomaly using ID nodes anticipated to be broadcastingwithin and external to the shipping container as well as generating thealert notification and transmitting that notification to the externaltransceiver unit to initiate a type of mediation response (such astriggering onboard fire suppression system 25010). Such code may bestored on a non-transitory computer-readable medium, such as memorystorage 26415 on command node 24160 (an embodiment of exemplary commandnode 26000) and memory storage 315 on ID nodes 24120 a-24120 i(embodiments of exemplary ID node 120 a). Thus, when executing suchcode, the ID nodes and the command node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 3600 and variations of that method.

A more detailed system embodiment similar to that described above (e.g.,that has ID nodes and a command node performing operations or steps fromthe exemplary methods disclosed above, including methods 3500 and 3600and variations of those methods) may include the fire suppression systemas part of the system itself along with the command node that monitorsID nodes within and external to the shipping container. Further detailedsystem embodiments may also include the external transceiver as afurther element that interacts with the system's command node andoperates to initiate different types of mediation responses at thedirection of the command node.

Monitoring for an Environmental Anomaly Via Selectively Assigned IDNodes

Additional embodiments may detect an environmental anomaly relative to ashipping container where an exemplary command node (e.g., ULD containernode that is essentially a master node that may not have locationcircuitry for self-locating capabilities, a mobile master node deployedon or as part of the shipping container that has location circuitry forself-locating capabilities) may selectively choose or assign which ofthe available ID nodes are to be monitored. In other words, embodimentsmay have a container's command node adaptively identify, choose, orotherwise assign a subset of the available ID nodes to function asdedicated monitor beacons that are deployed within the shippingcontainer and monitored as part of detecting an environmental anomalyrelated to the shipping container (e.g., a condition of the containerand/or package(s) or assets within the container). In general, theavailable ID nodes that may be assigned may be associated with aparticular package or packages within the container (e.g., travelingwith the package, attached to the package, inserted within the package,integrated as part of the package, and the like), may be associated withpart of the shipping container (e.g., attached to a wall, affixed to aceiling, integrated into the floor or base of the container, and thelike), or may be separately disposed within the container without beingfixed to or part of the container or a package/asset within thecontainer. As discussed in the embodiments described herein, the task ofselectively assigning such a subset of ID nodes may be based uponinformation about the ID node itself (e.g., the node's location withinthe container, whether the node is on a predetermined list of ID nodesto use as dedicated beacon monitors, whether the node is passivelydetected to be broadcasting by the container's command node);information regarding an item, asset, or package with which the ID nodemay be associated (e.g., shipping information indicating the type ofitem or asset being shipped in a package associated with an ID node,context data or location information (a loading scheme, pattern, orplan) indicating the location of a package associated with an ID node).Further, as described in more detail below, the selective assignment ofwhich ID nodes are used as the subset of ID nodes to be monitored maychange over time given that what may be stored within the container canchange as a shipping container loaded, unloaded, and/or re-arranged intransit or at any time, and ID nodes within the container may changeover time (e.g., ID nodes that are attached to the shipping containermay be replaced, ID nodes with packages may be removed from thecontainer or added to the container). As explained in more detail below,FIG. 37A through FIG. 40 provide further details on such embodimentsthat build upon the disclosure above.

FIGS. 37A-37B are diagrams of an exemplary shipping container (container24300 a) that leverages an exemplary wireless node network for detectingenvironmental anomalies associated with the shipping container using acommand node mounted to the shipping container and selectively assignedID nodes within (or as part of) the shipping container in accordancewith an embodiment of the invention. Referring now to FIG. 37A, anexemplary system 37000 is shown similar to what is described above withreference to, for example, FIGS. 31, 33, and 34 where a transit vehicle24200 is shown with transit vehicle storage 24205. The transit vehicle24200 is shown equipped with external transceiver 24150 (as previouslydescribed), which may communicate with remote control center server24100 via network 24105 as well as communicate directly with each ofcommand node 24160 and fire suppression system 25010. Within storage24205, exemplary shipping container 24300 a is disposed such that firesuppression system 25010 may be activated (e.g., by external transceiver24150 or by command node 24160) to supply a fire suppression agent intoshipping container 24300 a (e.g., as explained with reference to FIGS.32A-32C).

In more detail and as illustrated in FIG. 37A, the system's shippingcontainer 24300 a is deployed to include exemplary command node 24160,which may communicate with external transceiver 24150 as well as withfire suppression system 25010. Command node 24160 is further operativeto communicate with various ID nodes disposed within or as part ofcontainer 24300 a. For example, as shown in FIG. 37A, command node 24160is operative to communicate with exemplary ID nodes 24120 a-24120 gdisposed within container 24300 a. Exemplary ID nodes 24120 a-24120 c(i.e., ID Nodes 1-3) are illustrated as being respectively associatedwith packages 24400 a-24400 c, while ID nodes 24120 d-24120 g (i.e., IDNodes 4-7) are disposed within shipping container 24300 a without beingassociated with a package. As such, ID nodes 24120 d-24120 g (i.e., IDNodes 4-7) may be part of the shipping container or attached to theshipping container or may be simply an ID node disposed within theshipping container without being fixed to the shipping container andwithout being associated with, attached to, or disposed within a packagein the shipping container.

In FIG. 37B, system 37000 is graphically depicted as having command node24160 selectively assigning a subset of the ID nodes disposed withincontainer 24300 a (e.g., exemplary ID nodes 24120 a-24120 g) to functionas dedicated monitor beacons deployed within shipping container 24300 a.As shown in FIG. 37B, command node 24160 may have selectively assignedexemplary ID nodes 24120 a-24120 e and 24120 g to be the subset of IDnodes disposed in the container that are to be monitored as dedicatedmonitor beacons. As a dedicated monitor beacon, a particular ID nodewithin this subset (e.g., the highlighted subset of exemplary ID nodes24120 a-24120 e and 24120 g) will be monitored by command node 24160 foran unanticipated state of ceased broadcasting. The process ofselectively assigning the particular subset of those ID nodes disposedwithin container 24300 a to be those monitored as part of detecting anenvironmental anomaly related to the container may be performed in avariety of ways in different embodiments. For example, command node24160 may selectively assign particular ID nodes disposed within thecontainer 24300 a to be part of the monitored subset of ID nodes (i.e.,dedicated monitor beacons) based upon a predetermined (or updated) IDnode list maintained in memory of command node 24160; based upon such alist as well as location information (e.g., a type of context data) ondifferent ID nodes within the container 24300 a; based on such a list aswell as including additional ID nodes disposed within container 24300 athat are not on the list but are passively detected by the command node24160 as broadcasting; or based simply upon what ID nodes are disposedwithin container 24300 a that are passively detected by the command node24160. In further examples, command node 24160 may selectively assignwhich of the ID nodes are part of the monitored subset of ID nodesdisposed within the container 24300 a based on information related to apackage associated with a particular ID node. For instance, command node24160 may selectively assign which of the ID nodes are part of thesubset monitored based on shipping information that indicates what typeof item (or asset or object) is being shipped in the package, or basedon location information that indicates where the ID node's associatedpackage is located within the shipping container 24300 a. Further still,command node 24160 may receive instructions from, for example, externaltransceiver 24150 or server 24100 (via transceiver 24150 or directlyfrom server 24100) where such instructions identify the subset of whichID nodes are to function as the dedicated monitor beacons beingmonitored as part of detecting an environmental anomaly. Suchinstructions, in some embodiments, may take the form of vehicle statusdata associated with transit vehicle 24200 transporting shippingcontainer 24300 a and where the vehicle status data is indicative of thestate of transit vehicle 24200 (e.g., a takeoff vehicular status, acruising vehicle status, a landing vehicular status, and a stationaryvehicular status) and a risk factor associated with that state of thevehicle (e.g., a lower risk factor being when the transit vehicle is inthe stationary vehicular status).

Over time, the ID nodes disposed within a particular shipping containermay change. As such, embodiments may have the command node adjust whichof the ID nodes are in the assigned subset of ID nodes being monitoredas dedicated beacon nodes. FIGS. 38A-38B are diagrams of an exemplaryshipping container that leverages an exemplary wireless node network fordetecting environmental anomalies associated with the shipping containerusing a command node 24160 mounted to the shipping container 24300 a andselectively reassigned ID nodes within the shipping container 24300 awhen what is in shipping container 24300 a changes in accordance with anembodiment of the invention. Referring now to FIG. 38A, exemplaryshipping container 24300 a was originally in a configuration of havingthe ID nodes (i.e., ID nodes 24120 a-24120 g) disposed within it andwhere command node 24160 had selectively assigned a subset of those IDnodes (i.e., the highlighted subset of exemplary ID nodes 24120 a-24120e and 24120 g) as shown in FIG. 37B. But, as shown in FIG. 38A, package24400 a (having associated ID node 24120 a) has been removed fromcontainer 24300 a. In other words, a package having one of theselectively assigned ID nodes from the subset of monitored ID nodes(i.e., ID node 24120 a) is no longer disposed within shipping container24300 a. In this situation, command node 24160 may re-assign which ofthe ID nodes are to be monitored as dedicated monitors beacon so that,as shown in FIG. 38B, command node 24160 has now assigned a differentsubset of those ID nodes (i.e., the highlighted subset of exemplary IDnodes 24120 b-24120 e and 24120 g) to be monitored as dedicated monitorbeacons. In this way, an embodiment may deploy the command node 24160 toadjust for changes (e.g., loading, unloading, and even merere-arranging) of what is within shipping container 24300 a by adaptivelyreassigning which ID nodes are to be monitored.

In light of the embodiments illustrated in FIGS. 37A-37B and 38A-38B,exemplary system and method embodiments may be described in more detailthat involve selectively assigning particular ID nodes disposed within ashipping container (such as container 24300 a) when detecting anenvironmental anomaly related to the shipping container. For example,FIG. 39 is a flow diagram illustrating an exemplary method formonitoring a shipping container for an environmental anomaly using acommand node mounted to the shipping container and selective ones of aplurality of ID nodes disposed at different locations within theshipping container in accordance with an embodiment of the invention. Inparticular, FIG. 39 describes an exemplary improved method 3900 formonitoring a shipping container (e.g., shipping container 24300 a) foran environmental anomaly. The shipping container involved in method 3900may be transported on a transit vehicle (e.g., transit vehicle 24200shown in FIGS. 37A-38B—such as an aircraft, railway conveyance, amaritime vessel, or a roadway conveyance) that may also transportmultiple packages (e.g., packages 24400 a-24400 c as shown in FIGS.37A-38B). The wireless node network involved in method 3900 has at leasta plurality of ID nodes (e.g., ID node 24120 a-24120 g as shown in FIGS.37A-38B) and a command node associated with the shipping container(e.g., command node 241260 associated with and mounted to shippingcontainer 24300 a). The command node used as part of method 3900 may,for example, be implemented as a container node integrated as part ofthe shipping container or a self-locating master node implementedseparately from the shipping container. The ID nodes used as part ofmethod 3900 include ID nodes disposed within the shipping container(e.g., ID nodes 24120 a-24120 g) and, in particular, selectivelyassigned ones of those ID nodes as chosen or assigned by the commandnode. In this configuration, the command node involved in method 3900 isoperative to communicate with each of the ID nodes and an externaltransceiver unit associated with the transit vehicle (e.g., externaltransceiver 24150 on transit vehicle 24200).

Referring now to FIG. 39, exemplary method 3900 begins at step 3905 withthe command node selectively assigning a subset of the ID nodes disposedwithin a shipping container to function as dedicated monitor beaconsdeployed within the shipping container. For example, exemplary commandnode 24160 mounted to shipping container 24300 a as shown in FIG. 37Amay selectively assign ID nodes 2410 a-24120 e and 24120 g (i.e., IDnodes 1-5 and ID node 7 as shown in FIG. 37B) as the subset of ID nodesdisposed within shipping container 24300 a to function as dedicatedmonitor beacons out of those ID nodes disposed within shipping container24300 a (i.e., ID nodes 1-7).

At step 3910, method 3900 proceeds with the command node monitoring theassigned subset of the ID nodes for an unanticipated state of ceasedbroadcasting from any of the assigned subset of the ID nodes from step3905. For example, command node 24160 shown in FIG. 37B may monitor theassigned subset of ID nodes 2410 a-24120 e and 24120 g (i.e., ID nodes1-5 and ID node 7) as they are disposed within shipping container 24300a. Those assigned ID nodes are shown dispersed within shipping container24300 a—some being disposed near the walls of the container, some beingon the floor of the container, and some disposed within packages (orattached to packages). In this way, the command node 24160 isprogrammatically configured to allow for selective and adaptivemonitoring within the shipping container 24300 a. The assigned subset ofID nodes 2410 a-24120 e and 24120 g is anticipated to be broadcasting,as may be reflected by the communication profile data on each of thosenodes (as indicated in profile data 430 on command node 24160). Such acommunication profile may define an anticipated periodic broadcastbehavior for a node, and any shift in broadcast behavior from thatanticipated behavior may be indicative of an unanticipated state ofceased broadcasting.

At step 3915, method 3900 proceeds with the command node identifying anyof those in the assigned subset of the ID nodes found to be in theunanticipated state of ceased broadcasting based upon the monitoringstep 3910. In more detail, monitored broadcast signals from the assignedsubset of the ID nodes may indicate the source of such broadcastsignals—namely, which ID node is broadcasting the signal received by thecommand node as part of monitoring step 3910. As such, the command nodemay receive and assess the received broadcast signals and identify whichof the assigned subset of ID nodes are broadcasting as anticipated andwhich, if any, of the assigned subset of ID nodes are no longerbroadcasting as anticipated. Those no longer broadcasting as anticipateare identified by the command node as part of step 3915.

At step 3920, method 3900 continues with the command node adding any ofthe identified ID nodes from step 3915 to an unresponsive group from theassigned subset of the ID nodes found to be in the unanticipated stateof ceased broadcasting. Then, at decision step 3925, method 3900 has thecommand node determining if the size of the unresponsive group of theassigned subset of the ID nodes exceeds a threshold setting maintainedby the command node. If so, method 3900 proceeds from step 3925 directlyto step 3930 where the command node detects the environmental anomalyfor the shipping container because the size of the identified orotherwise sensed unresponsive group from the assigned subset of ID nodesexceeds the threshold setting. If not, method 3900 proceeds from step3925 back to step 3910 where monitoring of the assigned subset of IDnodes disposed within the shipping container by the command nodecontinues.

At step 3935, method 3900 proceeds with the command node automaticallygenerating an alert notification about the detected environmentalanomaly for the shipping container, and then in step 3940, method 3900has the command node transmitting the alert notification to thetransceiver unit (e.g., external transceiver 24150) to initiate amediation response related to the detected environmental anomaly.

In further embodiments of exemplary method 3900, step 3905 may be moredetailed in how the command node selectively assigns which of the IDnodes to be part of the assigned subset of ID nodes disposed within theshipping container to function as dedicated monitor beacons. Forexample, a more detailed embodiment may have the command nodeselectively assigning the subset of ID nodes as part of step 3905 byaccessing a predetermined ID node list in memory of the command node(e.g., list information on ID nodes to be monitored as part of contextdata 26560) and selectively assigning, by the command node, members ofthe subset of the ID nodes based upon which of the ID nodes areindicated in the accessed predetermined ID node list. A furtherembodiment may selectively assign members of the subset of the ID nodesas part of step 3905 by accessing both such a predetermine ID node listas well as context data having location information (e.g., another partof context data 26560) related to each of the ID nodes identified in thepredetermined ID node list, and then selectively assigning, by thecommand node, members of the subset of the ID nodes based upon which ofthe ID nodes are indicated in the accessed predetermined ID node listand the location information related to each of the ID nodes in thesubset of the ID nodes.

Still a further embodiment of method 3900 may selectively assign membersof the subset of the ID nodes as part of step 3905 using such apredetermined ID node list as well as detecting what other ID nodes arebroadcasting that are not on the list. In more detail, such a furtherembodiment of method 3900 may selectively assign members of the subsetof the ID nodes as part of step 3905 by having the command nodeaccessing a predetermined ID node list in memory of the command node;initially assigning a first set of members of the subset of the ID nodesbased upon which of the ID nodes are indicated in the accessedpredetermined ID node list; detecting, by the command node, a broadcastsignal from one or more additional ones of the ID nodes not included inthe predetermined ID node list; and selectively adding, by the commandnode, at least one additional ID node as an additional member of thesubset of the ID nodes from the additional ones of the ID nodes notincluded in the predetermined ID node list.

Yet another further embodiment of method 3900 may selectively assignmembers of the subset of the ID nodes as part of step 3905 by having thecommand node detecting a broadcast signal from one or more of the IDnodes; and selectively assigning members of the subset of the ID nodesfrom the those of the ID nodes detected as broadcasting. In more detail,such an embodiment may selectively assign members of the subset of theID nodes as part of step 3905 by having the command node detect one ormore broadcast signals respectively from one or more of the ID nodes;accessing, by the command node, a communication profile maintained bythe command node on an anticipated broadcasting state for each of theone or more of the ID nodes associated with the detected broadcastsignals; and selectively assigning, by the command node, members of thesubset of the ID nodes from those of the one or more of the ID nodesassociated with the detected broadcast signals that are in theanticipated broadcasting state according to their respectivecommunication profile.

In embodiments where the shipping container maintains packagesrespectively associated with each of the subset of the ID nodes, furtherembodiments of method 3900 may have the command node selectivelyassigning the subset of the ID nodes at step 3905 by having the commandnode access shipping information (e.g., a part of context data 26560 orprofile data 430) on what type of item is being shipped in each of thepackages associated with each of the ID nodes; and selectivelyassigning, by the command node, members of the subset of the ID nodesbased upon the type of item being shipped in each of the packagesassociated with each of the ID nodes in the subset of the ID nodes. Forexample, the command node may selectively assign the members of the IDnode subset by identifying which of the ID nodes are associated withpackages containing incendiary material based upon the shippinginformation; and assigning the identified ID nodes associated withincendiary material as the members of the subset of the ID nodes tofunction as the dedicated monitor beacons. In even more detail, thecommand node may assign only a predetermined number of the identified IDnodes associated with incendiary material as the members of the subsetof the ID nodes to function as the dedicated monitor beacons.

Further embodiments of method 3900 may selectively assign what ID nodesare in the monitored subset from step 3905 based on the package locationwithin the shipping container. In more detail, when the shippingcontainer maintains packages respectively associated with each of thesubset of the ID nodes, a further embodiment of step 3905 may have thecommand node accessing context data maintained by the command node onlocation information related to each the packages as maintained withinthe shipping container, and then selectively assigning the members ofthe subset of the ID nodes based upon the location information relatedto each of the ID nodes in the subset of the ID nodes. In even moredetail, a further embodiment may selectively assign such members of thesubset of ID nodes by identifying which of the ID nodes are located indesignated regions within the shipping container based upon the locationinformation (e.g., a loading scheme for the packages maintained withinthe shipping container, where the loading scheme is part of the locationinformation in the context data, such as context data 26560); andassigning a respective one of the ID nodes in each of the designatedregions within the shipping container as the members of the subset of IDnodes to function as the dedicated monitor beacons.

Still further embodiments may identify the subset of the ID nodes tofunction as the dedicated monitor beacons based upon an instructionmessage received by the command node. Such an instruction message may begenerated by a higher level element in the wireless node network, suchas the external transceiver (e.g., transceiver 24150) disposed on thetransit vehicle and separate from the shipping container as a higherlevel element of the network, or a server (e.g., server 24100) separatefrom the transit vehicle as an additional higher level element in thewireless node network.

Another further embodiment of method 3900 may have the command nodeselectively assign the subset of ID nodes in step 3905 based uponfurther contextual information on the transit vehicle and its status. Inmore detail, an embodiment of step 3905 may have the command nodereceiving vehicle status data provided by the external transceiver unitassociated with the transit vehicle (e.g., external transceiver 24150)and then have the command node selectively assigning the subset of theID nodes depending upon a state of the transit vehicle as indicated bythe vehicle status data. In even more detail, selectively assigning thesubset of the ID nodes may depend on a risk factor associated with thestate of the transit vehicle as indicated by the vehicle status data.For example, when the risk factor is a first level for a first state ofthe transit vehicle, a number of the members selectively assigned to thesubset of the ID nodes is a first value and when the risk factor is asecond level for a second state of the transit vehicle where the secondlevel is higher than the first level, the number of the membersselectively assigned to the subset of the ID nodes is greater than thefirst value. This, effectively, allows for the command node to operateto selectively assign the members of the ID nodes to be monitored bytaking into account a state of the transit vehicle (e.g., a takeoffvehicular status, a cruising vehicle status, a landing vehicular status,and a stationary vehicular status).

Embodiments of exemplary method 3900 may be extended to adapt to changesin what is stored in the shipping container (e.g., similar to thatdescribed with respect to FIGS. 38A-38B). In more detail, method 3900may further include the step of re-assigning which of the ID nodes aremembers of the subset of the ID nodes when the command node detects achange in what is maintained within the shipping container (e.g., whenthe command node finds the location of an ID node within the subset ofthe ID nodes being monitored is outside the shipping container, or whenthe command node is notified of an ID node within the subset of the IDnodes being monitored is removed from the shipping container). Moreparticularly, method 3900 may include re-assigning which of the ID nodesare members of the subset of the ID nodes when the command node detectsmovement within the shipping container using a motion detector on thecommand node (e.g., when sensor 26465 on command node 24160 is a motiondetector, and movement within shipping container 24300 a is detected viathat sensor indicating a change of what is within shipping container24300 a). Such re-assigning may be initiated from updated shippinginformation received by the command node on updated contents to bemaintained within the shipping container. As such, the command node mayre-assign which of the ID nodes are members of the subset of the IDnodes when the command node detects the change in what is maintainedwithin the shipping container based upon the updated shippinginformation. In such further embodiments, the re-assigning may comprisechanging which of the ID nodes are part of the subset of the ID nodeswhen the command node detects a loading operation of the shippingcontainer based on the updated shipping information, or detects anunloading operation of the shipping container based on the updatedshipping information, or detects a re-arrangement operation of theshipping container based upon detecting a change in location of at leastone of the members of the subset of the ID nodes within the shippingcontainer.

Further embodiments of method 3900 may involve more specific mediationresponses. For example, step 3940 may have the mediation response thatis initiated by the alert notification transmission to be an automaticresponse request for the external transceiver to activate a triggeredfire suppression system on the transit vehicle (e.g., exemplary firesuppression system 25010). In another example, step 3940 may have themediation response that is initiated by the alert notificationtransmission to be a request to change course of the transit vehiclefrom an existing travel path of the transit vehicle (e.g., a requestedprompt to be displayed on the external transceiver's display) or arequest to investigate the shipping container (e.g., a requested promptalso displayed on the external transceiver's display).

Additional embodiment of method 3900 may involve updating informationused in selectively assigning the subset of ID nodes and/or thethreshold setting used for detecting the environmental anomaly. Forexample, a further embodiment of method 3900 may include having thecommand node receiving a threshold update for the threshold settingmaintained by the command node used as part of step 3925. This thresholdupdate may be received from, for example, the external transceiver unit(e.g., as defined from user input provided by an operator of the transitvehicle or a logistics crew member of the transit vehicle using theexternal transceiver unit). This threshold update may also be providedto the external transceiver unit (e.g., transceiver 24150) from a remotecontrol center in communication with the external transceiver unit(e.g., server 24100). In another example, a further embodiment of method3900 may include having the command node receiving a selection updatefor which of the ID nodes are selectively assigned to be in the subsetof the ID nodes. This selection update may be received from, forexample, the external transceiver unit (e.g., as defined from user inputprovided by an operator of the transit vehicle or a logistics crewmember of the transit vehicle using the external transceiver unit). Thisselection update may also be provided to the external transceiver unit(e.g., transceiver 24150) from a remote control center in communicationwith the external transceiver unit (e.g., server 24100).

Embodiments of method 3900 may also implement step 3910 as monitoringthat involves confirming the validity of what the command node receives.In more detail, the monitoring step 3910 of method 3900 may beimplemented in a further embodiment by having the command node (a)receiving a communication broadcasted from a first of the ID nodeswithin the assigned subset of the ID nodes; (b) confirming the validityof the received communication; and (c) repeating steps (a) and (b) forthe remainder of the communications received from any of the remainingones of the ID nodes within the assigned subset of the ID nodes. Assuch, the identifying in step 3915 may then involve having the commandnode identifying the unresponsive group from the assigned subset of theID nodes based upon the monitoring step and based upon steps (a)-(c).

Further detailed implements may involve active or passive validation. Inan active validation example, the step of confirming the validity of thereceived communication in step (b) may have the command node sending anauthentication request to the first of the ID nodes within the assignedsubset of the ID nodes; and then receiving a validation response fromthe first of the ID nodes within the assigned subset of the ID nodesthat authenticates the communication broadcasted from the first of theID nodes within the assigned subset of the ID nodes. Alternatively, in apassive validation example, the step of confirming the validity of thereceived communication in step (b) may have the command node accessing avalidation sequence for the first of the ID nodes within the assignedsubset of the ID nodes, the validation sequence being maintained by thecommand node and characterizing expected broadcasts from the first ofthe ID nodes within the assigned subset of the ID nodes; and thendetermining if the received communication from the first of the ID nodeswithin the assigned subset of the ID nodes matches a predetermined oneof the expected broadcasts from the first of the ID nodes within theassigned subset of the ID nodes according to the validation sequencestored within the command node. Such a predetermined one of the expectedbroadcasts may be a rotating value previously received by the commandnode for the first of the ID nodes within the assigned subset of the IDnodes.

As noted above, the ID nodes used as part of method 3900 include IDnodes disposed within the shipping container (e.g., ID nodes 24120a-24120 g) and may be ID nodes respectively associated with one or moreof different packages within the shipping container, where each of theID nodes may travel with their respective one of the packages, beaffixed to the outside of one of the packages, be integrated as part ofone of the packages. In other embodiments, the ID nodes disposed withinthe container used as part of method 3900 may not be associated with anyof package disposed within the shipping container and, in some cases,may be temporarily or permanently fixed to a part of the shippingcontainer itself. In still another embodiment, the ID nodes used as partof method 3900 may be a combination of ID nodes associated with packagesand ID nodes not associated with any package.

Those skilled in the art will appreciate that method 3900 as disclosedand explained above in various embodiments may be implemented using animproved monitoring system for detecting and responding to anenvironmental anomaly in a shipping container having a plurality ofpackages and being transported by a transit vehicle having an externaltransceiver unit separate from the shipping container such as thatexplained above with reference to FIGS. 27A-28B and their respectiveexemplary elements. Such an embodiment of an improved monitoring system,as explained above relative to operations according to method 3900 andwith elements from system 37000 of FIG. 37A or system 38000 of FIG. 38A,uses at least multiple ID nodes disposed within the shipping container(e.g., ID nodes 24120 a-24120 g) running one or more ID node monitoringprogram code as part of node control and management code 325 to controloperations of the ID nodes to generate and broadcast signals, as well asa command node mounted to the shipping container (e.g., command node24160 in FIGS. 37A and 38A) running one or more parts of CN control &management code 26425 to control the operations of the command node aspart of monitoring for and detecting an environmental anomaly usingselectively assigned ones of the ID nodes that are monitored asdedicated monitor beacons. Such code may be stored on a non-transitorycomputer-readable medium, such as memory storage 26415 on command node24160 (an embodiment of exemplary command node 26000) and memory storage315 on ID nodes 24120 a-24120 g (embodiments of exemplary ID node 120a). Thus, when executing such code, the ID nodes and the command nodemay be operative to perform operations or steps from the exemplarymethods disclosed above, including method 3900 and variations of thatmethod.

A more detailed system embodiment may include the command node (e.g.,exemplary command node 24160 as shown in FIGS. 37A-38B), ID nodesdisposed within the shipping container (and that may be selectivelyassigned to a subset of the ID nodes to function as dedicated monitorbeacons, such as ID nodes 24120 a-24120 g as shown in FIGS. 27A-28B), aswell as the external transceiver (e.g., exemplary external transceiver24150) in communication with the command node. FIG. 40 is a diagram thatprovides more details regarding an exemplary external transceiver thatmay be activated and deployed on a transit vehicle for initiating amediation action in response to a detected environmental anomaly relatedto a shipping container being transported on the transit vehicle inaccordance with an embodiment of the invention. As generally explainedin above, embodiments of the external transceiver 24150 may receivealert notifications from the command node 24160, and automaticallyrespond to such alerts by initiating a mediation response related to aparticular mediation action based upon the particular environmentalanomaly detected. And as noted above, some mediation responses may havethe external transceiver 24150 triggering a fire suppression system25010 on transit vehicle 24200, communicating with an operator orlogistics crew aboard transit vehicle 24200, and/or communicating withremote control center server 24100 over network 24105. As shown in FIG.40, exemplary external transceiver 24150 may be implemented with atransceiver controller 40005, a transceiver communication interface40010 coupled to the controller, a display 40015 coupled to thecontroller, and a user input interface 40020 coupled to the controller.In general, the transceiver controller 40005 may be implemented using acore programmable microprocessor-based controller board with memory,processing, interface circuitry, and drivers (such as the Raspberry Pisingle board computer described above). The transceiver communicationinterface 40010 coupled to controller 40005 may be a wirelessreceiver/transmitter with a related antenna operative to communicatewith command node 24160 and onboard fire suppression system 25010 usinga wireless communication format (e.g., cellular, Wi-Fi, and the like).Transceiver communication interface 40010 may also include a wiredreceiver/transmitter with related driver and/or buffer circuitry thatallows for communication over wired connections when desired with suchother components (e.g., the fire suppression system 25010). The display40015 may be implemented as a screen type of interface (e.g., an LCDdisplay for the operator or crew, a touch screen display) or a moresimplified set of status lights allowing more simplified prompts andfeedback interaction with the operator or logistics crew that are on thetransit vehicle 24200. A further embodiment of display 40015 may beimplemented to display information via sound—e.g., with promptedmessages being displayed as an audible message (e.g., sounds, alarms,beeps, recited oral statements corresponding to details of the message,and the like) rather than a visual message. The user input interface40020 on the transceiver may be implemented using, for example, atouchscreen interface, interactive buttons, hardware keys, soft keys,switches, or other feedback input devices that accept information (e.g.,feedback input) from users (such as the operator or logistics crew thatare on the transit vehicle 24200). Such feedback input may be, forexample, from a logistics crew member that was prompted to inspect ashipping container (e.g., container 24300 a) and then provides feedbackinput via interface 40020. Those skilled in the art will appreciate thatsuch exemplary components that make up exemplary external transceiver24150 as shown in FIG. 41 may be applicable in any other embodiment thatmay use an external transceiver on the transit vehicle (e.g., externaltransceiver 25010, or cockpit transceiver 25150 a, or logisticstransceiver 25150 b).

In light of the above-described further details of an exemplary externaltransceiver (which may be implemented as cockpit transceiver 25150 a orlogistics transceiver 25150 b), further details appear below. This moredetailed system embodiment includes at least multiple ID nodes disposedat different locations within the shipping container, where each of theID nodes is configured to wirelessly transmit a broadcast signal. SuchID nodes may be, for example, ID nodes 24120 a-24120 g as shown in FIG.37B disposed within shipping container 24300 a. The system furtherincludes a command node mounted to the shipping container, such asexemplary command node 24160 as shown in FIG. 37B. The command nodefurther comprises a command node processing unit or processor (e.g.,processor 26400), a command node memory (e.g., memory 26415 and/ormemory 26420), and two communication interfaces (e.g., interfaces 26480,26485). The command node memory is coupled to the command nodeprocessing unit and maintains at least a command node containermanagement program code (e.g., a part of CN control and management code26425), and a threshold setting used for identifying the environmentalanomaly (e.g., another part of CN control and management code 26425). Afirst of the communication interfaces (e.g., short range communicationinterface 26480) is coupled to the command node processing unit, andconfigured to communicate using a first wireless communication formatcompatible with the broadcast signal transmitted by each of the IDnodes, while a second of the communication interfaces (e.g., medium/longrange communication interface 26485) is also coupled to the command nodeprocessing unit, and is configured to communicate using a secondwireless communications format (such as a cellular, Wi-Fi, or Bluetoothdepending on the deployed embodiment and its environment). The systemalso includes an external transceiver (e.g., external transceiver 25010,or cockpit transceiver 25150 a, or logistics transceiver 25150 b)mounted to the transit vehicle and configured to wirelessly communicatewith at least the second communication interface of the command nodeusing the second wireless communications format.

In operation, the command node's processing unit is programmaticallyconfigured, when executing the command node container management programcode, to be operative to selectively assign a subset of the ID nodes tofunction as dedicated monitor beacons deployed within the shippingcontainer, and then monitor the assigned subset of the ID nodes usingthe first communication interface for an unanticipated state of ceasedbroadcasting from any of the assigned subset of the ID nodes. Thecommand node processing unit is further programmatically configured tobe operative to identify an unresponsive group from the assigned subsetof the ID nodes to be in the unanticipated state of ceased broadcastingbased upon the monitoring operation involving the assigned subset of theID nodes; detect the environmental anomaly when a size of theunresponsive group of the assigned subset of the ID nodes exceeds thethreshold setting maintained by the command node; automatically generatean alert notification related to the detected environmental anomaly forthe shipping container; and cause the second communication interface totransmit the alert notification to the external transceiver unit toinitiate a mediation response related to the detected environmentalanomaly. The system's external transceiver is then operative to receivethe alert notification and initiate a mediation response related to thedetected environmental anomaly.

A further embodiment of such a system may equip the external transceiverto have a display interface (e.g., display 40015) that generates amediation response prompt related to the detected environmental anomalyin response to receiving the alert notification from the command node.In more detail, the external transceiver may be operative to initiatethe mediation response related to the detected environmental anomaly bygenerating the mediation response prompt on the display interface for anoperator of the transit vehicle. Such a mediation response prompt mayrequest a change in course of the transit vehicle from an existingtravel path of the transit vehicle in response to the detectedenvironmental anomaly. Alternatively, the external transceiver may beoperative to initiate the mediation response related to the detectedenvironmental anomaly by generating the mediation response prompt on thedisplay interface for a logistics crew member of the transit vehicle.Such a mediation response prompt may request an inspection of theshipping container in response to the detected environmental anomaly. Inthis manner, the alert notification received by the system's externaltransceiver may prompt personnel on the transit vehicle to initiate aparticular and selective type of mediation response as determined,identified, and initiated by the command node.

In still another additional embodiment of such a system, the system mayfurther include an onboard triggered fire suppression system (e.g.,exemplary fire suppression system 25010 as shown in FIGS. 32A-32C) as anelement of the system. The system's onboard fire suppression system isdisposed on the transit vehicle for responsively supplying a firesuppression agent to the shipping container in response to an activationsignal received by the onboard triggered fire suppression system fromthe external transceiver. In this way, the system's external transceivermay initiate the mediation response by generating the activation signalwhen it receives the alert notification from the command node, whichcauses the external transceiver to send the activation signal to theonboard triggered fire suppression system on the transit vehicle.

In a more detailed embodiment, the system may include an onboardtriggered fire suppression system (e.g., exemplary fire suppressionsystem shown in FIGS. 32A-32C), as well as having a more detailedexternal transceiver deployed to have a display interface (e.g., display40015 on exemplary transceiver 24150 shown in FIG. 40) that generates amediation response prompt related to the detected environmental anomalyin response to receiving the alert notification from the command node.The more detailed external transceiver may also be deployed as having auser input interface (e.g., user input interface 40020 on exemplarytransceiver 24150 shown in FIG. 40) that receives feedback inputresponsive to the mediation response prompt displayed on the displayinterface. As such, the system's external transceiver may then befurther operative to generate the activation signal in response toreceiving the feedback input, and send the activation signal to thesystem's onboard triggered fire suppression system on the transitvehicle. The feedback input, for example as part of this further systemembodiment, may be input from a logistics crew member of the transitvehicle after an inspection of the shipping container prompted by themediation response prompt generated on the display interface of theexternal transceiver. Thus, such feedback input may be provided to auser input interface on exemplary logistics transceiver 25150 b by alogistics crew member on aircraft 2500 after inspecting a particularshipping container.

In still another system embodiment, an exemplary improved monitoringsystem may be deployed for detecting and responding to an environmentalanomaly in a shipping container having a packages and being transportedby a transit vehicle. In general, such a system comprises at least acommand node mounted to the shipping container (e.g., affixed to thecontainer or integrated as part of the container), ID nodes disposedwithin the container, and an onboard fire suppression system responsiveto an activation signal sent by the command node directly to the firesuppression system. In this system embodiment, an initial mediationresponse is initiated directly by the command node's alert notificationto the fire suppression system, while a secondary mediation response mayalso be initiated when the command node transmits the alert notificationto an external transceiver, which may have a display for promptsinvolving course changes for the transit vehicle or requests to inspectthe shipping container. Feedback input through the external transceivermay initiate a secondary activation of the fire suppression system.

In more detail, such an exemplary system embodiment includes at leastmultiple ID nodes disposed at different locations within the shippingcontainer, where each of the ID nodes is configured to wirelesslytransmit a broadcast signal. Such ID nodes may be, for example, ID nodes24120 a-24120 g as shown in FIG. 37B disposed within shipping container24300 a. The system further includes a command node mounted to theshipping container, such as exemplary command node 24160 as shown inFIG. 37B. The command node further comprises a command node processingunit or processor (e.g., processor 26400), a command node memory (e.g.,memory 26415 and/or memory 26420), and two communication interfaces(e.g., interfaces 26480, 26485). The command node memory is coupled tothe command node processing unit and maintains at least a command nodecontainer management program code (e.g., a part of CN control andmanagement code 26425), and a threshold setting used for identifying theenvironmental anomaly (e.g., another part of CN control and managementcode 26425). A first of the communication interfaces (e.g., short rangecommunication interface 26480) is coupled to the command node processingunit, and configured to communicate using a first wireless communicationformat compatible with the broadcast signal transmitted by each of theID nodes, while a second of the communication interfaces (e.g.,medium/long range communication interface 26485) is also coupled to thecommand node processing unit, and is configured to communicate using asecond wireless communications format (such as a cellular, Wi-Fi, orBluetooth depending on the deployed embodiment and its environment). Thesystem also includes an onboard triggered fire suppression system (e.g.,exemplary fire suppression system 25010 as shown in FIG. 37B as well asin more detail in FIGS. 32A-32C) disposed on the transit vehicle forresponsively supplying a fire suppression agent to the shippingcontainer in response to an activation signal directly received by theonboard triggered fire suppression system from the second communicationinterface of the command node.

As the ID nodes broadcast, the processing unit of the system's commandnode is programmatically configured, when executing the command nodecontainer management program code, to be operative to selectively assigna subset of the ID nodes to function as dedicated monitor beaconsdeployed within the shipping container and monitor the assigned subsetof the ID nodes using the first communication interface for anunanticipated state of ceased broadcasting from any of the assignedsubset of the ID nodes. The command node processing unit is furtheroperative to then identify an unresponsive group from the assignedsubset of the ID nodes to be in the unanticipated state of ceasedbroadcasting based upon the monitoring, and then detect theenvironmental anomaly when a size of the unresponsive group of theassigned subset of the ID nodes exceeds the threshold setting maintainedby the command node. In response to this detection, the command nodeprocessing unit is further operative to automatically generate an alertnotification related to the detected environmental anomaly for theshipping container, and cause the second communication interface totransmit the alert notification to the onboard triggered firesuppression system to directly initiate a mediation response by theonboard triggered fire suppression system related to the detectedenvironmental anomaly. The system's onboard triggered fire suppressionsystem is then operative to receive the alert notification as theactivation signal and initiate a mediation response related to thedetected environmental anomaly by responsively supplying the firesuppression agent to the shipping container.

The system may further include, as an additional element, an externaltransceiver (e.g., exemplary external transceiver 24150) mounted to thetransit vehicle and configured (e.g., as described with respect to theembodiment shown in FIG. 40 and the transceiver communication interface40010) to wirelessly communicate with at least the second communicationinterface of the command node using the second wireless communicationsformat. This system's external transceiver also has a display interface(e.g., display 40015) that generates a mediation response prompt relatedto the detected environmental anomaly, such as a displayed mediationprompt message. As such, the command node processing unit may be furtheroperative to cause the second communication interface to transmit thealert notification to the external transceiver to initiate a secondarymediation response related to the detected environmental anomaly, suchas requesting that an operator of the transit vehicle change the courseof the transit vehicle from an existing travel path of the transitvehicle in response to the detected environmental anomaly or requestinga logistics crew member of the transit vehicle conduct an inspection ofthe shipping container in response to the detected environmentalanomaly.

In more detail, the system's external transceiver may also include auser input interface (e.g., user input interface 40020) that may receivefeedback input (e.g., input from a logistics crew member of the transitvehicle after an inspection of the shipping container) responsive to themediation response prompt displayed on the display interface. As such,the external transceiver may then generate a secondary activation signalin response to receiving the feedback input, and transmit the secondaryactivation signal to the onboard triggered fire suppression system onthe transit vehicle. The system's onboard triggered fire suppressionsystem may then supply an additional amount of the fire suppressionagent to within the shipping container in response to receiving thesecondary activation signal from the external transceiver.

Further embodiments that involve a command node interacting withselectively assigned ID nodes when monitoring for and detecting anenvironmental anomaly may focus on the shipping container itself as aspecially enhanced and improved type of apparatus. FIGS. 41A-41D arediagrams of different exemplary improved and enhanced shippingcontainers that transports packages and self-monitors for anenvironmental anomaly using selectively assigned ID nodes in accordancewith an embodiment of the invention. FIG. 41A shows such an enhancedshipping container with ID nodes attached to parts of the shippingcontainer, while FIG. 41B shows ID nodes integrated into parts of theshipping container. FIG. 41C shows packages loaded into such an enhancedshipping container and FIG. 41D illustrates how the container's commandnode may selectively assign particular ones of the container's ID nodesas a subset of ID nodes to use for monitoring for and detecting anenvironmental anomaly related to the shipping container.

Referring now to FIG. 41A, further details of an embodiment of exemplaryshipping container 24300 a are shown. In particular, FIG. 41Aillustrates shipping container 24300 a as having command node 24160mounted to it as well as ID nodes 1-10 (24120 a-24120 j, respectively)disposed within container 24300 a. In general, the exemplary shippingcontainer 24300 a has a base 41005, a plurality of walls 41010 coupledto the base 41005, a ceiling 41015 coupled to the walls 41010 so as toenclose the walls 41010 and base 41005. As such, the base 41005, thewalls 41010, and the ceiling 41015 collectively define an interiorstorage space within the shipping container 24300 a. While not shown inFIG. 41A, those skilled in the art will appreciate that an embodiment ofshipping container 24300 a may further include at least one selectivelysecurable door (e.g., a lid as part of the ceiling, an access hatch ordoor as part of at least one of the walls) that provides securableaccess into the interior storage space of the shipping container.

ID nodes 1-10 (24120 a-24120 j) disposed within container 24300 a, asshown in FIG. 41A, are located in different locations along the interiorof the shipping container 24300 a. In more detail, ID nodes 1-2 are eachdisposed at different locations as part of ceiling 41015; ID nodes 3-6are each disposed at different locations as part of floor/base 41005;and ID nodes 7-10 are each disposed at different locations as part ofwalls 41010. As disposed on these different locations within theshipping container 24300 a, each of ID nodes 1-10 are configured towirelessly transmit a broadcast signal (e.g., an advertising signalbroadcast by the ID node that may be requesting information, reportingstatus information on the node, transmitting sensor data gathered by theID node, relaying shared sensor data from another ID node, and thelike). As shown in FIG. 41A, exemplary ID nodes 1-10 (24120 a-24120 j)may be disposed on the different locations as being fixed to an interiorsurface of the shipping container, or removable and only temporarilyattached to the shipping container. Thus, an embodiment may use some orall of the ID nodes disposed within shipping container 24300 a as beingreplaceable to allow for periodic replacement (e.g., swapping out IDnodes that need charging, repair, or replacement) with the same type ofID node or with a different ID node having batteries that have a longercharge life, having longer range or different communication capabilities(e.g., use a longer range communicating format to better communicatewith command node 24160), or having specialized sensors (e.g., an IDnode used for monitoring special and/or hazardous items being shippedwithin the container where the sensors on the ID node may correspond toparticular risks associated with such items, correspond to temperatureor other environmental conditions critical for monitoring such items,and the like).

Alternatively, the ID nodes disposed within the shipping container maybe integrated into parts of the shipping container as shown in FIG. 41B.Referring now to FIG. 41B, exemplary ID nodes 1-10 (24120 a-24120 j)disposed within container 24300 a are located in different locations ofthe shipping container 24300 a, but are shown as disposed as integratedparts of shipping container 24300 a. As shown, ID nodes 1-2 are eachdisposed at different locations as integrated parts of ceiling 41015(e.g., within the ceiling); ID nodes 3-6 are each disposed at differentlocations as integrated parts of floor/base 41005; and ID nodes 7-10 areeach disposed at different locations as integrated parts of differentwalls 41010.

FIG. 41C shows exemplary ID nodes 1-10 (24120 a-24120 j) disposed withincontainer 24300 a after packages 24400 a-24400 d have been loaded intocontainer 24300 a. As shown in FIG. 41C, packages 24400 a-24400 c areeach associated with ID nodes 24120 k-24120 m, respectively. In moredetail, each of packages 24400 a-24400 c may have their respective IDnodes 24120 k-24120 m attached to the outside of the respective package,inserted within the interior of the respective package, attached to theitem/asset within the respective package, or integrated as parts of therespective package in such a way that the ID node and its associatedpackage are logically related to one another as well as physicallytraveling together within the shipping container 24300 a.

The command node 24160 mounted to shipping container 24300 a, as shownin FIG. 41C, is similar to the command node used in other systemembodiments described above in that it has a command node processingunit; a command node memory coupled to the processor and maintaining atleast a command node container management program code used toselectively assign ID nodes to be monitored when detecting anenvironmental anomaly, and a threshold setting used for identifying theenvironmental anomaly; and two communication interfaces—one fortransmitting and receiving in a first wireless communication formatcompatible with the broadcast signal transmitted by each of the IDnodes, and the other for transmitting and receiving in a second wirelesscommunications format (e.g., cellular, Wi-Fi, or other formats). In moredetail, the enhanced shipping container's command node may, for example,be implemented as a container node integrated as part of the shippingcontainer or, alternatively, be implemented as self-locating master nodeimplemented separately from the shipping container (but where it may besimply attached to the container).

In operation, the enhanced shipping container's command node processoris programmatically configured, when executing the command nodecontainer management program code, to be operative to selectively assigna subset of the ID nodes to function as dedicated monitor beaconsdeployed as part of the shipping container (e.g., selectively assigningID nodes 3-7, 10, 11, and 13 as illustrated in FIG. 41D); monitor theassigned subset of the ID nodes using the first communication interfacefor an unanticipated state of ceased broadcasting from any of theassigned subset of the ID nodes; identify an unresponsive group from theassigned subset of the ID nodes to be in the unanticipated state ofceased broadcasting based upon the monitoring step; detect theenvironmental anomaly when a size of the unresponsive group of theassigned subset of the ID nodes exceeds the threshold setting maintainedby the command node; automatically generate an alert notificationrelated to the detected environmental anomaly for the shippingcontainer; and cause the second communication interface to transmit thealert notification to directly cause a mediation response related to thedetected environmental anomaly.

In more detail, a further apparatus embodiment may have the commandnode's processor causing the second communication interface to transmitthe alert notification to directly cause the mediation response by beingfurther operative to cause the second communication interface totransmit the alert notification to a fire suppression apparatus disposedoutside the shipping container (e.g., fire suppression system 25010shown in FIG. 41D) to cause the fire suppression apparatus toresponsively supply a fire suppression agent to the shipping containeras the mediation response (as explained in more detail with respect toFIGS. 32A-32C). In this way, alert notification transmitted by theenhanced shipping container's command node 24160 to the fire suppressionsystem 25010 activates the fire suppression system 25010 to cause thefire suppression system to pierce shipping container 24300 a and injectfire suppression agent into the interior storage space of the shippingcontainer as the mediation response.

Still another embodiment of such an enhanced shipping containerapparatus may have the command node's processor causing the secondcommunication interface to transmit the alert notification to directlycause the mediation response by being further operative to cause thesecond communication interface to transmit the alert notification to anexternal transceiver disposed outside of the shipping container (e.g.,external transceiver 24150, cockpit transceiver 25150 a, or logisticstransceiver 25150 b). In this way, the alert notification sent by thecommand node's second communication interface causes the externaltransceiver to generate a prompt to investigate the shipping containeror to change course from a transit path related to the shippingcontainer.

In yet another embodiment of such an enhanced shipping containerapparatus may have the command node's memory maintaining a predeterminedID node list identifying those of the ID nodes to be monitored. As such,the command node's processor may then be operative to selectively assignthe subset of the ID nodes by being further programmatically configuredto be operative to access the predetermined ID node list from thecommand node memory, and selectively assign members of the subset of theID nodes based upon which of the ID nodes disposed within the shippingcontainer are indicated in the accessed predetermined ID node list.

In a similar way, another embodiment of such an enhanced shippingcontainer apparatus may have the command node's memory maintaining apredetermined ID node list identifying those of the ID nodes to bemonitored as well as context data on location information related to alocation for each of the ID nodes disposed as part of the shippingcontainer. As such, the command node's processor may then be operativeto selectively assign the subset of the ID nodes by being furtherprogrammatically configured to be operative to access the predeterminedID node list and the context data from the command node memory, andselectively assign members of the subset of the ID nodes based uponwhich of the ID nodes are indicated in the accessed predetermined IDnode list and the location information related to each of the ID nodesin the subset of the ID nodes.

In even more detail, another embodiment of such an enhanced shippingcontainer apparatus may have the command node's memory maintaining apredetermined ID node list identifying those of the ID nodes to bemonitored. As such, the command node's processor may then be operativeto selectively assign the subset of the ID nodes by being furtherprogrammatically configured to be operative to access the predeterminedID node list from the command node memory; initially assign a first setof members of the subset of the ID nodes based upon which of the IDnodes are indicated in the accessed predetermined ID node list; causethe first communication interface to detect a broadcast signal from oneor more additional ones of the ID nodes not included in thepredetermined ID node list; and selectively add at least one additionalID node as an additional member of the subset of the ID nodes from theadditional ones of the ID nodes not included in the predetermined IDnode list.

In still another embodiment, the enhanced shipping container apparatusmay selectively assign the subset of ID nodes to be monitored in more ofa passive detection manner. In particular, such an embodiment of theenhanced shipping container apparatus may have the command nodeprocessing unit being operative to selectively assign the subset of theID nodes by being further programmatically configured to be operative tocause the first communication interface to detect the broadcast signalfrom one or more of the ID nodes, and selectively assign members of thesubset of the ID nodes from the ID nodes detected as broadcasting. Inmore detail, the embodiment of the enhanced shipping container apparatusmay have the command node's memory maintaining a communication profile(e.g., part of profile data 430) that identifies an anticipatedbroadcasting state for ID nodes disposed within the enhanced shippingcontainer. As such, the command node processing unit may be operative toselectively assign the subset of the ID nodes by being furtherprogrammatically configured to be operative to cause the firstcommunication interface to detect one or more of the broadcast signalsrespectively from one or more of the ID nodes; access the communicationprofile from the command node memory to determine the anticipatedbroadcasting state for each of the one or more of the ID nodesassociated with the detected broadcast signals; and selectively assignmembers of the subset of the ID nodes from those of the one or more ofthe ID nodes associated with the detected broadcast signals that are inthe anticipated broadcasting state according to their respectivecommunication profile.

The enhanced shipping container's command node may, in some embodiments,receive (via the second communication interface) an instruction messagethat identifies the subset of the ID nodes to function as the dedicatedmonitor beacons. Such an instruction message received by the commandnode may be generated by an external transceiver disposed outside andseparate from the shipping container (e.g., exemplary externaltransceiver 24150) or a server (e.g., server 24100) in communicationwith the shipping container's command node (e.g., either directlybetween command node 24160 and server 24100 or indirectly from commandnode 24160 and at least one intermediary device (e.g., externaltransceiver 24150) in communication with server 24100.

Embodiments of the enhanced shipping container may adapt which ID nodesare monitored as part of detecting an environmental anomaly based uponwhat may be stored within the container. In particular, an embodimentmay have the command node processing unit being further operative tore-assign which of the ID nodes are the members of the subset of the IDnodes being monitored when the command node detects a change in what ismaintained within the shipping container. In more detail, the commandnode element of the enhanced shipping container apparatus may include amotion detector (e.g., a type of sensor 26465) coupled to the commandnode processing unit. Such a motion detector is disposed within theshipping container and operative to generate a movement detection signalupon detecting movement within the shipping container. As such, hecommand node processing unit may then be operative to detect the changein what is maintained within the shipping container based upon themovement detection signal from the motion detector within the shippingcontainer. For example, the motion detector may generate a movementdetection signal when the container is being loaded, unloaded, orpackages/items/assets are moved within the container.

In another example, the command node processing unit on the enhancedshipping container apparatus may be operative to detect the change inwhat is maintained within the shipping container (and responsivelyre-assign which ID nodes to use as the monitored subset) based uponreceiving updated shipping information on updated contents to bemaintained within the shipping container. As such, the shippingcontainer's command node may detect a loading operation, an unloadingoperation, or a re-arrangement operation of the shipping container basedon the updated shipping information. Such a re-arrangement operation ofthe shipping container, which may cause such re-assigning of the IDnodes in the subset, may be also be based upon detecting a change inlocation of at least one of the members of the subset of the ID nodeswithin the shipping container.

In even more detail, another embodiment of such an enhanced shippingcontainer apparatus may have the command node's memory maintaining acommunication profile that identifies an anticipated broadcasting statefor each of ID nodes within the shipping container apparatus. As such,the command node's processor may then be operative to selectively assignthe subset of the ID nodes by being further programmatically configuredto be operative to monitor the assigned subset of the ID nodes for theunanticipated state of ceased broadcasting from any of the assignedsubset of the ID nodes according to the communication profile maintainedin the command node memory. Such a communication profile, in moredetail, may define an anticipated periodic broadcast behavior for themember of the assigned subset of the ID nodes, so that the command nodeprocessing unit may be operative to monitor the assigned subset of theID nodes for the unanticipated state of ceased broadcasting by beingfurther operative to monitor for a shift in broadcast behavior of any ofthe members of the assigned subset of the ID nodes away from theanticipated broadcast behavior for the respective member of the assignedsubset of the ID nodes.

Embodiments of the enhanced shipping container may have its command nodeaccess and use contextual type of data when selectively assigning whichID nodes to use as part of the monitored subset. In particular, theenhanced shipping container's command node processor may receive vehiclestatus data provided by the external transceiver via the secondcommunication interface; and then be operative to selectively assign thesubset of the ID nodes depending upon a state of the transit vehicle(e.g., a takeoff vehicular status, a cruising vehicle status, a landingvehicular status, and a stationary vehicular status) as indicated by thevehicle status data or, in more detail, depending on a risk factorassociated with the state of the transit vehicle as indicated by thevehicle status data. For example, the risk factor associated with aparticular state of the vehicle may allow for different numbers of IDnodes to be assigned to the monitored subset. As such, when the riskfactor is a first level for a first state of the transit vehicle, anumber of the members selectively assigned to the subset of the ID nodesmay be a first value. When the risk factor is a second level for asecond state of the transit vehicle where the second level is higherthan the first level, the number of the members selectively assigned tothe subset of the ID nodes may be greater than the first value. Thus,under certain conditions where the vehicle status data reflects a higherrisk factor, the command node may selectively assign an increased numberof ID nodes disposed within the enhanced shipping container to bemonitored as part of detecting an environmental anomaly related to theenhanced shipping container.

In a further embodiment, the enhanced shipping container's command nodeprocessing unit may receive a threshold update for the threshold settingover the second communication interface from, for example, from theexternal transceiver unit (e.g., as defined by an operator of thetransit vehicle using the external transceiver unit, or as defined by alogistics crew member of the transit vehicle using the externaltransceiver unit). Such a threshold update may be provided to theexternal transceiver unit from a remote control center (e.g., server24100 as shown in FIG. 41D) in communication with the externaltransceiver unit. In like manner, the enhanced shipping container'scommand node processing unit may receive a selection update over thesecond communication interface, where the selection update has updatedinformation on which of the ID nodes are selectively assigned to be inthe subset of the ID nodes (e.g., updated information for thepredetermined ID node list that may be used by the command node to knowwhich ID nodes disposed within the enhanced shipping container tomonitor). Such a selection update may be provided, for example, from theexternal transceiver unit (e.g., as defined by an operator of thetransit vehicle using the external transceiver unit, or as defined by alogistics crew member of the transit vehicle using the externaltransceiver unit). Such a threshold update may be provided to theexternal transceiver unit from a remote control center (e.g., server24100 as shown in FIG. 41D) in communication with the externaltransceiver unit. In this way, an embodiment of the enhanced shippingcontainer may be adaptively and automatically repurposed and updated onwhich ID nodes to use as dedicated monitor beacons and what type ofthreshold setting to use based on how the container may be deployed andwhat the container may be carrying.

Additionally, an embodiment of the enhanced shipping container may haveits command node confirming the validity of broadcasts received from theID nodes. In particular, an embodiment may have the enhanced commandnode processor being operative to monitor the assigned subset of the IDnodes for the unanticipated state of ceased broadcasting by beingfurther operative to (a) receive a communication broadcasted from afirst of the ID nodes within the assigned subset of the ID nodes overthe first communication interface; (b) confirm the validity of thereceived communication; and then (c) repeating (a) and (b) for theremainder of the communications received from any of the remaining onesof the ID nodes within the assigned subset of the ID nodes. As such, thecommand node may be operative to then identify the unresponsive groupfrom the assigned subset of the ID nodes based upon the monitoring stepand based upon steps (a)-(c). In a further “active” validation example,the command node processing unit may confirm the validity of thereceived communication in (b) by being further operative to (b1) send,via the first communication interface, an authentication request to thefirst of the ID nodes within the assigned subset of the ID nodes; and(b2) receive, via the first communication interface, a validationresponse from the first of the ID nodes within the assigned subset ofthe ID nodes that authenticates the communication broadcasted from thefirst of the ID nodes within the assigned subset of the ID nodes. In afurther “passive” validation example, the command node memory maymaintain a validation sequence for the first of the ID nodes within theassigned subset of the ID nodes, where the validation sequencecharacterizes expected broadcasts from the first of the ID nodes withinthe assigned subset of the ID nodes; and then the command node processormay confirm the validity of the received communication in (b) by beingfurther operative to (b1) access the validation sequence from thecommand node memory; and (b2) determine if the received communicationfrom the first of the ID nodes within the assigned subset of the IDnodes matches a predetermined one of the expected broadcasts from thefirst of the ID nodes within the assigned subset of the ID nodesaccording to the validation sequence stored within the command node.Such a predetermined one of the expected broadcasts may be implementedas a rotating value previously received by the command node over thesecond communication interface for the first of the ID nodes within theassigned subset of the ID nodes.

Enhanced Deployment of ID Nodes for Detecting Environmental Anomaly

As noted in the embodiments described above, an exemplary command node(e.g., a container node that is essentially a master node that may nothave location circuitry for self-locating capabilities, or a mobilemaster node deployed on or as part of the shipping container that haslocation circuitry for self-locating capabilities) may selectivelychoose, assign, or designate which of the available ID nodes are to bemonitored as part of detecting an environmental anomaly. However, attimes, one of the assigned ID nodes to be monitored may fall outside areception range of the command node. As such, further embodiments mayhave an ID node within a container being designated (or pre-designated)as listeners/bridging nodes so that other ID nodes that are to be usedfor monitoring environmental anomalies but located outside the commandnode's reception range (e.g., remotely located ID nodes functioning asmonitor beacons) can still communicate with the command node andparticipate as part of an enhanced monitoring system for shippingcontainer environmental anomalies.

In some embodiments, this may be helpful when proactively setting up theset of monitoring ID nodes so as to accommodate shipped items known toshield communications with certain nodes. In further embodiments, as thecontainer is loaded, the command node mounted on the shipping containermay “see” or be able to communicate with an ID node designated formonitoring environmental anomalies (i.e., one from the group of monitorbeacons), but then detects a drop in signal strength from that ID node.The command node may then adaptively and responsively re-program anotherID node to operate as a bridged listening node for the ID node desiredto be one of the container's environmental anomaly detecting elementsbut no longer able to be received by the command node as it was earlierin the container loading process. In further embodiments, the commandnode may dynamically alter how often the ID nodes report based on adensity of RF broadcasters within the reception range of the commandnode (e.g., lowering a reporting interval when the density of RFbroadcasters is above a threshold RF visibility limit, and increasing areporting interval when such a density falls below the threshold limit).Embodiments may also have the command node instructing particular IDnodes functioning as members of the group of monitor beacons todynamically adjust their respective RF broadcast signal output power aspackages are loaded to help increase the likelihood of still “seeing”node-enabled packages at extreme reaches of the container relative tothe command node.

Further details of exemplary embodiments are illustrated in FIGS.42A-43. FIGS. 42A-42C are diagrams of an exemplary shipping containerthat leverages an exemplary wireless node network for detectingenvironmental anomalies associated with the shipping container using acommand node mounted to the shipping container and selectively assignedID nodes within the shipping container as a group of monitor beaconsincluding a dedicated bridging node for a remote monitor beacon inaccordance with an embodiment of the invention. Referring now to FIG.42A, exemplary system 42000 is shown with exemplary shipping container24300 a having command node 24160 mounted to the shipping container24300 a and ID nodes 24120 a-24120 g (also referred to as ID nodes 1-7)disposed at different locations within container 24300 a. ID nodes 1, 2,3, and 5 are associated with respective ones of packages 24400 a-24400 dmaintained within shipping container 24300 a, while ID nodes 4, 6, and 7are not associated with any particular package maintained withincontainer 24300 a. Notably, as shown in FIG. 42A, ID node 4 is disposedalong the floor or base of shipping container 24300 a and is notassociated with any particular package within container 24300 a. In anexample, ID node 4 may be operative to wirelessly broadcast a signal(e.g., an advertising signal, a signal having sensor data generated byID node 4, and the like), which may be received by command node 24160.However, as packages are loaded within shipping container 24300 a (suchas package 3 and package 4 (i.e., packages 24400 c and 24400 d)), thematerial within such packages may reduce the reception range 42005 ofcommand node. In other words, with packages loaded within shippingcontainer 24300 a, ID node 4 may be beyond the reception range 42005 ofcommand node 24160 where command node 24160 could receive wirelesslybroadcast signals from ID node 4 prior to particular packages havingbeen loaded into container 24300 a. Thus, as shown in FIG. 42B, ifcommand node 24160 initially selected ID node 4 as part a group of theID nodes to be monitor beacons selected (e.g., ID nodes 1, 2, 4, and 5deployed in different locations within the container 24300 a and chosenfor monitoring as part of detecting an environmental anomaly within theshipping container 24300 a), ID node 4 may be or have become a remotemonitor beacon because it is or has become located outside of areception range 42005 for the short range communication interface 26480used by the command node 24160 to communicate with ID nodes. Rather thansimply dropping ID node 4 from the group of monitor beacons, commandnode 24160 may still include ID node 4 as part of the selected group ofmonitor beacons (e.g., ID nodes 1, 2, 4, and 5) by programmaticallyconfiguring another of the ID nodes in the shipping container (e.g., IDnode 3) to be a dedicated bridging node as shown in FIG. 42C. As such,dedicated bridging ID node 3, as configured to relay communications insuch an embodiment, is operative to provide a dedicated intermediarycommunication link between the command node 24160 and the remote monitorbeacon (i.e., ID node 4 in this example). ID node 3, as the dedicatedbridging node, is located and deployed within the reception range 42005of the first communication interface 26480 on the command node 24160 anda broadcast range of the remote monitor beacon so that the command node24160 may receive signals broadcast by ID node 4 (the remote monitorbeacon) as relayed by ID node 3 (the dedicated bridging node for such aremote monitor beacon). In this way, while materials in package 3 andpackage 4 may shield, attenuate, and/or otherwise interfere withcommunications between command node 24160 and ID node 4, the use of IDnode 3 as a dedicated bridging node permits the continued ability ofcommand node 24160 to use ID node 4 as a monitor beacon for detecting anenvironmental anomaly. While the embodiments shown in FIGS. 42A-42Cillustrate how the command node 24160 may configure an ID node to be adedicated bridging node for a remote monitor beacon, those skilled inthe art will appreciate that a system involving such a command node24160 may configure multiple ID nodes to be different dedicated bridgingnodes for different remote monitor beacons used when detecting anenvironmental anomaly on shipping container 24300 a.

In more detail, an embodiment of an improved system for adaptivelymonitoring for an environmental anomaly related to a shipping container(e.g., container 24300 a) maintaining a plurality of packages (e.g.,packages 1-4) may generally have multiple ID nodes (e.g., ID nodes 1-7)disposed as different locations within the shipping container and acommand node (e.g., command node 24160) mounted to the shippingcontainer. The system may have the shipping container being transportedby a transit vehicle (such as an airplane, a railway conveyance, amaritime vessel, and a roadway conveyance). The system's command nodehas at least a command node processing unit (commonly referred to as aprocessor), a command node memory, and two communication interfaces withwhich the command node uses to the communicate with ID nodes within theshipping container and to communication with further elements (e.g.,exemplary external transceiver 24150 (which may be a mobile handheldtransceiver or a transceiver fixed to a relative location, such as ontransit vehicle 24200), exemplary onboard triggered fire suppressionsystem 25010), such as explained with reference to FIG. 26 and exemplarycommand node 26000. The system's command node may, for example, beimplemented as a container node integrated as part of the shippingcontainer or, alternatively, a master node implemented separately fromthe shipping container but attached to the container. In more detail,the system's command node has command node memory coupled to the commandnode processing unit and maintaining at least a command node containermanagement program code (e.g., CN control and management code 26425),and a threshold setting used for identifying the environmental anomaly(e.g., a threshold setting as part of code 26425). The command node'sfirst communication interface (e.g., interface 26480) is coupled to thecommand node processing unit and is configured to communicate using afirst wireless communication format compatible with each of the ID nodes(e.g., Bluetooth Low Energy, ZigBee, and the like). The command node'ssecond communication interface (e.g., interface 26485) is also coupledto the command node processing unit and is configured to communicatewith devices disposed separately from the shipping container (e.g., anexternal transceiver unit associated with a transit vehicle transportingthe shipping container, an onboard fire suppression system) using asecond wireless communications format.

In operation, the system's command node is specially programmed,adapted, and configured, when executing the command node containermanagement program code, to be operative to first select a group ofmonitor beacons from the ID nodes disposed within the shippingcontainer. Each in the selected group of monitor beacons are what thecommand node will monitor as part of detecting any environmental anomalyrelated to the shipping container. Each member of the group of monitorbeacons broadcasts according to a communication profile associated withthat member of the group of monitor beacons (e.g., a communicationprofile that is part of profile data 430). Each member of the group ofmonitor beacons is deployed at a different location within the shippingcontainer, and where the group of monitor beacons includes at least aremote monitor beacon located outside a reception range of the firstcommunication interface on the command node. For example, command node24160 may select ID nodes 1, 2, 4, and 5 (as shown in FIG. 42A-C) to bea group of monitor beacons where ID node 4 is a remote monitor beacon asit is outside the reception range 42005 of the command node. In moredetail, the remote monitor beacon may be located outside the receptionrange of the command node as a result of at least one of the packagesbeing loaded within the shipping container (such as when package 4 shownin FIG. 42C is loaded within shipping container 24300 a and placed ontop of ID node 4). Prior to such loading, the command node processingunit may initially receive the respective broadcast signal directly fromthe remote monitor beacon before the relevant package(s) is loadedwithin the shipping container, and then the command node processing unitmay detect the loss of direct reception of the respective broadcastsignal from the remote monitor beacon after the at least one of thepackages is loaded within the shipping container.

The command node processing unit is further operative, as part of thesystem's operation, to programmatically configure at least another ofthe ID nodes not included in the selected group of monitor beacons to bea dedicated bridging node (e.g., ID node 3 as shown in FIG. 42C). Thededicated bridging node provides a dedicated intermediary communicationlink between the command node and the remote monitor beacon. In otherwords, the dedicated bridging node is deployed within the receptionrange of the first communication interface on the command node and abroadcast range of the remote monitor beacon so as to operate as a relaytype of node to enable the command node to effectively receivewirelessly broadcast signals from the remote monitor beacon via relayedcommunications from the dedicated bridging node to the command node. Inmore detail, such a dedicated monitor beacon may be a pre-designated oneof the ID nodes not included in the group of monitor beacons to be thededicated bridging node, or may be an adaptively designated one of theID nodes not included in the group of monitor beacons to be thededicated bridging node (such as when the command node detects a drop insignal strength from one member of the group of monitor beacons). Forexample, the command node may detect, using the first communicationinterface, the drop in signal strength transmitted from a member of thegroup of monitor beacons as the shipping container is being loaded, andthen responsively and programmatically configure a second of the IDnodes not included in the group of monitor beacons to be the dedicatedbridging node providing the dedicated intermediary communication linkbetween the command node and the one member of the group of monitorbeacons.

The command node processing unit of the system's command node is furtheroperative to receive, via the first communication interface, arespective broadcast signal from each respective member of the group ofmonitor beacons. In more detail, the command node directly receives therespective broadcast signal from the group of monitor beacons notincluding the remote monitor beacon, but indirectly receives therespective broadcast signal from the remote monitor beacon through thededicated intermediary communication link provided by the dedicatedbridging node. As such, the command node processing unit is thenoperative to monitor the received respective broadcast signals from thegroup of monitor beacons for an unanticipated state of ceasedbroadcasting from any of the group of monitor beacons; identify anunresponsive subset from the group of monitor beacons to be in theunanticipated state of ceased broadcasting based upon the monitoringstep; and detect the environmental anomaly when a size of theunresponsive subset of the group of monitor beacons exceeds thethreshold setting maintained by the command node in the command nodememory.

Once detected, the command node processing unit is then operative toautomatically generate an alert notification related to the detectedenvironmental anomaly for the shipping container, and cause the secondcommunication interface to transmit the alert notification to initiate amediation response related to the detected environmental anomaly. Thesystem may further include an external transceiver unit disposedseparately from the shipping container (e.g., exemplary externaltransceiver 24150 (mobile or a fixed transceiver), cockpit transceiver25150 a, or logistics transceiver 25150 b). The transmitted alertnotification may be sent to the external transceiver, which is operativeto receive the alert notification and initiate the mediation responserelated to the detected environmental anomaly (as described in moredetail above related to mediation prompts to be displayed and requestingfeedback input related to such a detected environmental anomaly). Thesystem, in a further embodiment, may include an onboard fire suppressionsystem (e.g., fire suppression system 25010) disposed separately fromthe shipping container and that can supply a fire suppression agentwithin the shipping container. The transmitted alert notification, inthis embodiment, may be sent directly to the onboard fire suppressionsystem by the command node so that the onboard fire suppression systemreceives the alert notification and responsively initiates the mediationresponse related to the detected environmental anomaly (e.g., suppliesthe fire suppression agent to the interior of the shipping container).

In a further embodiment of this system, the command node processing unitmay select the group of monitor beacons by being furtherprogrammatically configured to be operative to cause the firstcommunication interface to transmit a monitor activation command to eachof the group of monitor beacons to cause each of the group of monitorbeacons to broadcast the respective broadcast signal from each of thegroup of monitor beacons.

In further embodiments, the system's command node may dynamically alterhow often the ID node members of the group of monitor beacons broadcast.In more detail, the command node processing unit may be furtheroperative to transmit, via the first communication interface, aninstruction to a first member of the group of monitor beacons to changehow often that member of the group of monitor beacons broadcasts itsrespective broadcast signal. Such an instruction may cause that memberof the group of monitor beacons to change how often the first member ofthe group of monitor beacons broadcasts its respective broadcast signalbased upon an active broadcasting density within the range of the firstmember of the group of monitor beacons. In another example, such aninstruction may be a command to cause the first member of the group ofmonitor beacons to lower a reporting interval of how often the firstmember of the group of monitor beacons broadcasts its respectivebroadcast signal when the active broadcasting density is above an RFvisibility limit, or to increase a reporting interval of how often thefirst member of the group of monitor beacons broadcasts its respectivebroadcast signal when the active broadcasting density is below an RFvisibility limit. In still another example, the command node processingunit may be operative to transmit, via the first communicationinterface, an instruction to each member of the group of monitor beaconsto change how often each member of the group of monitor beaconsbroadcasts its respective broadcast signal (as opposed to only onemember).

In still other embodiments, the system's command node may dynamicallyalter the RF output power of the monitor beacons (i.e., those ID nodesselected to be part of the group of monitor beacons) as packages areloaded. In more detail, the command node processing unit may be furtheroperative to transmit, via the first communication interface, aninstruction to a first member of the group of monitor beacons to changea power level setting for how the first member of the group of monitorbeacons broadcasts its respective broadcast signal. Such an instructionmay cause that member of the group of monitor beacons to change thepower level setting for how that member of the group of monitor beaconsbroadcasts its respective broadcast signal based upon context dataaccessible by the command node (e.g., context data 26560) and related toa proximity environment of that particular member of the group ofmonitor beacons (e.g., what items are in packages next to or within apredetermined distance to that member of the group of monitor beacons,what is in a package associated with that member of the group of monitorbeacons). In still another example, the command node processing unit maybe further operative to transmit, via the first communication interface,an instruction to each member of the group of monitor beacons to changea respective power level for how each member of the group of monitorbeacons broadcasts its respective broadcast signal. Such changes fordifferent members may be different depending on what is disposed next toor near respective members of the group of monitor beacons.

A further embodiment of the system's ID nodes, which may be part of thegroup of monitor beacons, may be associated with particular packages. Inmore detail, an embodiment may have the command node operative to selectat least a portion of the group of monitor beacons as having ID nodesassociated with respective ones of the packages maintained within theshipping container (e.g., ID node 1, 2, and 5 as shown in FIG. 42C). Inanother embodiment, at least a portion of the group of monitor beaconsmay include ID nodes traveling with respective ones of the packagesmaintained within the shipping container, or affixed to respective onesof the plurality of packages maintained within the shipping container,or integrated within respective ones of the plurality of packagesmaintained within the shipping container.

In further embodiments where packages may be associated with the IDnodes, the command node memory may have shipping information (e.g., atype of data that is part of association data 440) on what type of itemis being shipped in each of the packages associated with each of the IDnodes. As such, the command node processing unit may select the group ofmonitor beacons by being further operative to access the shippinginformation from the command node memory, and selectively assign themembers of the group of monitor beacons based upon the type of itembeing shipped in each of the packages associated with each of the IDnodes in the group of the monitor beacons as reflected in the accessedshipping information. In a more detailed embodiment, the command nodeprocessing unit may selectively assign the members of the group ofmonitor beacons by being further operative to identify which of the IDnodes are associated with packages containing predetermined targetmaterial for observation according to the accessed shipping information,and assign the identified ID nodes associated with the predeterminedtarget material for observation as members of the group of monitorbeacons. Such predetermined target material may include, for example,incendiary material, corrosive material, explosive material, flammablematerial, or acidic material. In another embodiment, the command nodeprocessing unit may selectively assign the members of the group ofmonitor beacons by being further operative to identify which of the IDnodes are associated with packages containing such predetermined targetmaterial for observation according to the accessed shipping information,and assign only a predetermined number of the identified ID nodesassociated with the predetermined target material for observation asmembers of the group of monitor beacons.

Further embodiments provide more details on why an ID node in the groupof monitor beacons may be unresponsive. For example, in one furtherembodiment, at least one of the ID nodes from the identifiedunresponsive subset from the group of monitor beacons is in theunanticipated state of ceased broadcasting due to mechanical damage. Inmore detail, the mechanical damage may, for example, be damage resultingfrom an impact to the ID node and damage resulting from exposure to apredetermined target material (such as a corrosive material, anexplosive material, or a flammable material). Further still, themechanical damage may be damage rendering the ID node from theidentified unresponsive subset from the group of monitor beacons to beinoperable as a result of an impact to the at least one of the ID nodesfrom the identified unresponsive subset from the group of monitorbeacons; corrosive damage to the ID node from the identifiedunresponsive subset from the group of monitor beacons; explosive damageto the ID node from the identified unresponsive subset from the group ofmonitor beacons; or flammable damage (e.g., heat damage, burn damage) tothe ID node from the identified unresponsive subset from the group ofmonitor beacons.

In a further embodiment, at least one of the ID nodes from theidentified unresponsive subset from the group of monitor beacons mayhave a particular type of ID node enclosure having an outer exposedmaterial is generally designed or engineered to fail. In other words,the node enclosure or part of the enclosure may lose structuralintegrity or break apart when exposed to an environmental anomaly, whichmay cause the ID node's battery to be disconnected. A portion of theenclosure may, for example, be weakened in a targeted way based on aparticular material anomaly to be detected. For instance, the nodeenclosure may react with a predetermined chemical material (or apredetermined incendiary material, predetermined flammable material, ora predetermined corrosive material). As such, an ID node with this IDnode enclosure becomes inoperable and uncommunicative after the outerexposed material has reacted with the predetermined material that maycome from an environmental anomaly. In an example, a node enclosure madewith a starch at a targeted point of the node enclosure so that, whenthat part dissolves when exposed to liquid or another predeterminedchemical, the portion of the node enclosure holding the battery mayseparate and, as a result, disconnect the battery in this example. Inanother example, the node enclosure or a part of the enclosure may bemade from a material which has chemical reaction with specificcomponents related to types of environmental anomalies (e.g., copperconnectors as part of the node enclosure that may operate as batteryterminals may dissolve when exposed to an acidic environment. Stillanother example may have a node enclosure or portion thereof and/or anelectric pathway part of the enclosure being built of a material with amelting point at or lower than a targeted environmental anomaly(temperature of a lithium-ion battery fire).

In still further embodiments, the threshold setting or the selectioncriteria for which ID nodes are part of the group of monitor beacons maybe remotely updated. For example, a further embodiment of the system mayhave the command node processing unit being further operative toreceive, via the second communication interface, a threshold update forthe threshold setting maintained by the command node. Such a thresholdupdate may be received from an external transceiver unit (e.g.,exemplary external transceiver 24150) and defined by an operator of thetransit vehicle using the external transceiver unit or a logistics crewmember of the transit vehicle using the external transceiver unit. Thethreshold update may, in another example, be provided to the externaltransceiver unit from a remote control center (e.g., server 24100) incommunication with the external transceiver unit. In another example,another further embodiment of the system may have the command nodeprocessing unit being further operative to receive, via the secondcommunication interface, a selection update for which of the ID nodesare selected to be in the group of monitor beacons. Such a selectionupdate may be received from an external transceiver unit (e.g.,exemplary external transceiver 24150) and defined by an operator of thetransit vehicle using the external transceiver unit or a logistics crewmember of the transit vehicle using the external transceiver unit. Theselection update may also be provided to the external transceiver unitfrom a remote control center (e.g., server 24100) in communication withthe external transceiver unit.

Another embodiment may include the external transceiver as an element ofthe improved system. In more detail, another embodiment of an improvedsystem for adaptively monitoring for an environmental anomaly related toa shipping container maintaining packages. The system generally includesmultiple ID nodes disposed at different locations within the shippingcontainer (where each of the ID nodes are configured to wirelesslybroadcast a signal), a command node mounted to the shipping container(as described above), and an external transceiver disposed separatelyfrom the shipping container that is configured to wirelessly communicatewith at least the second communication interface of the command nodeusing the second wireless communications format. The command nodeprocessing unit is programmatically configured, when executing thecommand node container management program code in its memory, to beoperative to first select a group of monitor beacons from the ID nodes.Each member of the group of monitor beacons is deployed at a differentlocation within the shipping container and broadcasts according to acommunication profile associated with that member of the group ofmonitor beacons, and where the group includes at least a remote monitorbeacon located outside a reception range of the first communicationinterface on the command node. In this improved system, the command nodeprocessing unit is also operative to programmatically configure at leastanother of the ID nodes not included in the group of monitor beacons tobe a dedicated bridging node providing a dedicated intermediarycommunication link between the command node and the remote monitorbeacon. The dedicated bridging node is deployed within the receptionrange of the first communication interface on the command node and abroadcast range of the remote monitor beacon. The command nodeprocessing unit is then operative to receive, via the firstcommunication interface, a respective broadcast signal from eachrespective member of the group of monitor beacons, where the commandnode directly receives the respective broadcast signal from the group ofmonitor beacons not including the remote monitor beacon, and where thecommand node indirectly receives the respective broadcast signal fromthe remote monitor beacon through the dedicated intermediarycommunication link provided by the dedicated bridging node. The commandnode processing unit is then operative to monitor the receivedrespective broadcast signals from the group of monitor beacons for anunanticipated state of ceased broadcasting from any of the group ofmonitor beacons; identify an unresponsive subset from the group ofmonitor beacons to be in the unanticipated state of ceased broadcastingbased upon the monitoring step; detect the environmental anomaly when asize of the unresponsive subset of the group of monitor beacons exceedsa threshold setting maintained by the command node; automaticallygenerate an alert notification related to the detected environmentalanomaly for the shipping container; and cause the second communicationinterface to transmit the alert notification to the external transceiverto initiate a mediation response related to the detected environmentalanomaly. The improved system's external transceiver is then operative toreceive the alert notification and initiate the mediation responserelated to the detected environmental anomaly.

In a further embodiment, the improved system's external transceiver mayhave a display interface (e.g., display 40015) that generates amediation response prompt related to the detected environmental anomalyin response to receiving the alert notification from the command node.In more detail, the external transceiver may initiate the mediationresponse related to the detected environmental anomaly by generating themediation response prompt on the display interface for an operator of atransit vehicle transporting the shipping container. The mediationresponse prompt may, for example, request the operator change in courseof the transit vehicle from an existing travel path of the transitvehicle in response to the detected environmental anomaly or request alogistics crew member to inspect the shipping container.

Another embodiment of the improved system may include an onboardtriggered fire suppression system disposed separately from the shippingcontainer, such as exemplary fire suppression system 25010. The onboardtriggered fire suppression system responsively supplies a firesuppression agent to the shipping container in response to an activationsignal received by the onboard triggered fire suppression system. Assuch, the system's external transceiver may initiate the mediationresponse by (a) generating the activation signal in response toreceiving the alert notification from the command node and (b) sendingthe activation signal to the onboard triggered fire suppression system.In more detail, the system's external transceiver may include a displayinterface that generates a mediation response prompt related to thedetected environmental anomaly in response to receiving the alertnotification from the command node, and a user input interface thatreceives feedback input responsive to the mediation response promptdisplayed on the display interface. As such, the improved system'sexternal transceiver may be further operative to generate the activationsignal in response to receiving the feedback input, and send theactivation signal to the onboard triggered fire suppression system. Thefeedback input may, for example, be input from a logistics crew memberof the transit vehicle of a transit vehicle transporting the shippingcontainer after an inspection of the shipping container prompted by themediation response prompt generated on the display interface of theexternal transceiver.

In still another embodiment of an improved system for adaptivelymonitoring for an environmental anomaly may involve having the onboardfire suppression system directly initiated by the command node toprovide the mediation response. As such, this further embodiment mayinclude multiple ID nodes disposed at different locations within theshipping container, a command node (as described above) mounted to theshipping container, and an onboard triggered fire suppression systemdisposed separately from the shipping container and operative toresponsively supply a fire suppression agent to the shipping containerin response to an activation signal received by the onboard triggeredfire suppression system from the second communication interface. Thecommand node's processing unit is programmatically configured, whenexecuting the command node container management program code, to beoperative to select the group of monitor beacons from the ID nodes (asdescribed above to include a remote monitor beacon located outside areception range of the first communication interface on the commandnode); programmatically configure at least another of the ID nodes notincluded in the group of monitor beacons to be a dedicated bridging node(as described above); receive a respective broadcast signal from eachrespective member of the group of monitor beacons (directly orindirectly from the remote monitor beacon vis the dedicated bridgingnode); monitor the received respective broadcast signals from the groupof monitor beacons for an unanticipated state of ceased broadcastingfrom any of the group of monitor beacons; identify an unresponsivesubset from the group of monitor beacons to be in the unanticipatedstate of ceased broadcasting based upon the monitoring step; detect theenvironmental anomaly when a size of the unresponsive subset of thegroup of monitor beacons exceeds a threshold setting maintained by thecommand node; automatically generate an alert notification related tothe detected environmental anomaly for the shipping container; and causethe second communication interface to transmit the alert notification tothe onboard triggered fire suppression system to directly initiate amediation response by the onboard triggered fire suppression systemrelated to the detected environmental anomaly. The system's onboardtriggered fire suppression system is then operative to receive the alertnotification as the activation signal and initiate the mediationresponse related to the detected environmental anomaly by responsivelysupplying the fire suppression agent to the shipping container.

A further embodiment may add an external transceiver disposed separatelyfrom the shipping container, where the external transceiver isconfigured to wirelessly communicate with at least the secondcommunication interface of the command node using the second wirelesscommunications format, and where the external transceiver further has adisplay interface that generates a mediation response prompt related tothe detected environmental anomaly. As such, the command node processingunit may be further operative to cause the second communicationinterface to transmit the alert notification to the external transceiverto initiate a secondary mediation response related to the detectedenvironmental anomaly. In one example, the secondary mediation responsemay be generating the mediation response prompt on the display interfaceof the external transceiver, where the mediation response promptrequests a change in course of a transit vehicle transporting theshipping container from an existing travel path of the transit vehiclein response to the detected environmental anomaly. In another example,the secondary mediation response may be generating the mediationresponse prompt on the display interface of the external transceiver,where the mediation response prompt requests an inspection of theshipping container in response to the detected environmental anomaly.The system's external transceiver may further include a user inputinterface that receives feedback input responsive to the mediationresponse prompt displayed on the display interface (e.g., feedback inputin the form of input received after an inspection of the shippingcontainer prompted by the mediation response prompt generated on thedisplay interface of the external transceiver), where the externaltransceiver is further operative to generate a secondary activationsignal in response to receiving the feedback input, and transmit thesecondary activation signal to the onboard triggered fire suppressionsystem. As such, the onboard triggered fire suppression system may thensupply an additional amount of the fire suppression agent to within theshipping container in response to receiving the secondary activationsignal from the external transceiver.

The operation of such exemplary improved systems may also take the formof methods for adaptively monitoring for an environmental anomaly usinga group of monitor beacons including a dedicated bridging node for aremote monitor beacon. FIG. 43 is a flow diagram illustrating such anexemplary method for adaptively monitoring for an environmental anomalyusing a group of monitor beacons including a dedicated bridging node fora remote monitor beacon in accordance with an embodiment of theinvention. Referring now to FIG. 43, method 4300 uses elements of awireless node network having at least ID nodes (e.g., ID nodes 1-5 shownin FIG. 42C) disposed within the shipping container (e.g., exemplaryshipping container 24300 a) and a command node (e.g., exemplary commandnode 24160) associated with the shipping container maintaining packages(e.g., packages 1-4 shown in FIG. 42C), where the command node isoperative to communicate with each of the ID nodes and an externaltransceiver unit (e.g., exemplary external transceiver 24150 as disposedon transit vehicle 24200) associated with a transit vehicle (e.g., anairplane, a railway conveyance, a maritime vessel, and a roadwayconveyance).

The ID nodes used as part of method 4300 may be not be associated withany particular package in the shipping container. However, in someembodiments of method 4300, the ID nodes used as all or at least aportion of the group of monitor beacons may be ID nodes associated withrespective ones of the packages maintained within the shippingcontainer. Such ID nodes associated with packages may travel with arespective package, be affixed to a respective package, or be integratedwithin a respective package.

Method 4300 begins at step 4305 with the command node designating agroup of monitor beacons from the ID nodes. Each member of the group ofmonitor beacons broadcasts according to a communication profileassociated with that member of the group of monitor beacons, and eachmember is an ID node deployed at a different location within theshipping container. As designated or selected by the command node aspart of step 4305, the group of monitor beacons includes at least aremote monitor beacon located outside a reception range of the commandnode. For example, exemplary command node 24160 may designate ID nodes1, 2, 4, and 5 as a group of monitor beacons shown within shippingcontainer 24300 in FIG. 42A-42C, where ID node 4 is a remote monitorbeacon located outside reception range 42005 for command node 24160. Inmore detail, step 4305 may be implemented by the command nodetransmitting a monitor activation command to each of the group ofmonitor beacons to cause each ID node in the group of monitor beacons tobroadcast the respective broadcast signal from each of the group ofmonitor beacons.

The remote monitor beacon designated as part of step 4305 may be locatedoutside the reception range of the command node as a result of at leastone of the packages being loaded within the shipping container. Forexample, ID node 4 (as shown in FIG. 42C) may qualify as a remotemonitor beacon once package 4 has been loaded into shipping container24300 a, which may place materials within package 4 in a location thatattenuates or shields electronic signals and effectively reduces thereception range of the command node 24160 so as to no longer receivewireless signals broadcast from ID node 4. As such, the command node24160 may initially receive broadcast signals directly from ID node 4(the remote monitor beacon) before package 4 is loaded within theshipping container, but not after package 4 is loaded. In such asituation, the command node 24160 may detect the loss of directreception of a respective broadcast signal from ID node 4 (i.e., theremote monitor beacon) after package 4 is loaded within the shippingcontainer and, thus, render ID node 4 as a remote monitor beacon.

In a further embodiment of step 4305 when designating the group ofmonitor beacons, each of the ID nodes designated as a monitor beacon maybe associated with a respective package maintained within the shippingcontainer. As such, designating the group of monitor beacons by thecommand node in step 4305 may have the command node accessing shippinginformation on what type of item is being shipped in each of thepackages associated with each of the ID nodes, and then selectivelyassigning members of the group of monitor beacons based upon the type ofitem being shipped in each of the packages associated with each of theID nodes in the group of the monitor beacons as reflected in theaccessed shipping information. In more detail, selectively assigningsuch members may be implemented with the command node identifying whichof the ID nodes are associated with packages containing predeterminedtarget material for observation according to the accessed shippinginformation, and then assigning the identified ID nodes associated withthe predetermined target material for observation material as themembers of the group of monitor beacons. Such predetermined targetmaterial for observation may include, for example, incendiary material,corrosive material, explosive material, flammable material, or acidicmaterial. Further still, selectively assigning such members may beimplemented by the command node identifying which of the ID nodes areassociated with packages containing predetermined target material forobservation material, and then assigning only a predetermined number ofthe identified ID nodes associated with the predetermined targetmaterial for observation material as members of the group of monitorbeacons.

At step 4310, method 4300 has the command node programmaticallyconfiguring another of the ID nodes not included in the group of monitorbeacons to be a dedicated bridging node for the remote monitor beacon.The dedicated bridging node (e.g., ID node 3 as shown in FIGS. 42A-42C)provides a dedicated intermediary communication link between the commandnode and the remote monitor beacon (e.g., ID node 4) as the dedicatedbridging node is deployed within the reception range of the command nodeand a broadcast range of the remote monitor beacon. For example, ID node4, as a remote monitor beacon, may wirelessly broadcast a signal thatcan be received by ID node 3, as a dedicated bridging node, and relayedto the command node 24160 by ID node 3.

In a further embodiment of step 4310, the command node mayprogrammatically configure such a dedicated monitor beacon byprogrammatically configuring a pre-designated one of the ID nodes notincluded in the group of monitor beacons to be the dedicated bridgingnode. As such, ID node 3 may be pre-designated as a dedicated bridgingnode. In another example, ID nodes not associated with particularpackages but fixed to or integrated as part of the shipping containermay be pre-designated due to their deployment location within theshipping container (e.g., being deployed along a periphery of thecontainer but not at the base of the container, while the command nodemay be located more central to the container for more optimum receptionrange coverage).

In still another embodiment, step 4310 may have the command nodeprogrammatically configuring the dedicated bridging node as thecontainer is being loaded. For example, the command node, as part ofstep 4310, may programmatically configure an adaptively designated oneof the ID nodes not included in the group of monitor beacons to be thededicated bridging node when the command node detects a drop in signalstrength from one member of the group of monitor beacons. This may beaccomplished by having the command node detecting the drop in signalstrength transmitted from the one member of the group of monitor beaconsas the shipping container is being loaded, and then programmaticallyconfiguring a second ID node not included in the group of monitorbeacons to be the dedicated bridging node providing the dedicatedintermediary communication link between the command node and the onemember of the group of monitor beacons.

At step 4315, method 4300 continues with the command node receiving arespective broadcast signal from each respective member of the group ofmonitor beacons (directly from the group of monitor beacons notincluding the remote monitor beacon, and indirectly from the remotemonitor beacon through the dedicated intermediary communication linkprovided by the dedicated bridging node). In some embodiments, method4300 may also have the command node instructing a member of the group ofmonitor beacons to change how often that member of the group of monitorbeacons broadcasts its respective broadcast signal. How often may dependupon an active broadcasting density within the range of that member ofthe group of monitor beacons as known or detected by the command node.The instruction to change how often a member of the group of monitorbeacons broadcasts may lower a reporting interval when the activebroadcasting density is above an RF visibility limit, or may increasethe reporting interval when the active broadcasting density is below anRF visibility limit. Furthermore, another embodiment of method 4300 mayhave the instruction sent to each member of the group of monitor beaconsso as to have the command node change how often each member of the groupof monitor beacons broadcasts its respective broadcast signal.

In a further embodiment, method 4300 may also have the commandinstruction a member of the group of monitor beacons to change a powerlevel setting for how that member of the group of monitor beaconsbroadcasts its respective broadcast signal. Such an instruction may, forexample, change the power level setting for how that member of the groupof monitor beacons broadcasts its respective broadcast signal based uponcontext data accessible by the command node and where the context datais related to a proximity environment of the first member of the groupof monitor beacons. Such an instruction, in another embodiment, may besent by the command node to each member of the group of monitor beaconsto change a respective power level for how each member of the group ofmonitor beacons broadcasts its respective broadcast signal. In this way,the command node may interact with the particular monitor beacons in away to proactively adjust for what materials may be next to the monitorbeacons that may interfere with communications from the monitor beaconto the command node.

At step 4320, method 4300 proceeds with the command node monitoring thereceived respective broadcast signals from the group of monitor beaconsfor an unanticipated state of ceased broadcasting from any of the groupof monitor beacons.

At step 4325, method 4300 has the command node identifying any from thegroup of monitor beacons that are in the unanticipated state of ceasedbroadcasting and then adding, in step 4330, those identified members ofthe group of monitor beacons to an unresponsive subset from the group ofmonitor beacons to be in the unanticipated state of ceased broadcastingbased upon the monitoring step 4320. Thus, at step 4330, method 4300 hasthe command node adding any of the identified ID nodes from step 4325 tothe unresponsive subset of those ID nodes in the group of monitorbeacons that are identified to be in the unanticipated state of ceasedbroadcasting. Then, at decision step 4335, method 4300 has the commandnode determining if a size of the unresponsive subset of the group ofmonitor beacons exceeds a threshold setting maintained by the commandnode. If so, method 4300 proceeds from step 4335 directly to step 4340where the command node detects the environmental anomaly for theshipping container because the size of the unresponsive group of monitorbeacons exceeds the threshold setting. If not, method 4300 proceeds fromstep 4335 back to step 4320.

At step 4340, method 4300 proceeds with the command node detecting theenvironmental anomaly when the size of the unresponsive subset of thegroup of monitor beacons exceeds the threshold setting maintained by thecommand node. In response, to detecting the environmental anomaly instep 4340, method 4300 then moves to step 4345 where the command nodeautomatically generates an alert notification related to the detectedenvironmental anomaly for the shipping container.

At step 4350, method 4300 proceeds with the command node transmittingthe alert notification to the external transceiver unit (e.g., exemplaryexternal transceiver 24150, exemplary cockpit transceiver 25150 a, orexemplary logistics transceiver 25150 b) to initiate a mediationresponse related to the detected environmental anomaly.

In a further embodiment of method 4300, the method may also includehaving the command node altering the threshold setting related todetecting the environmental anomaly or altering which ID nodes are to beselected as monitor beacons. In more detail, a further embodiment ofmethod 4300 may have the command node receiving a threshold update forthe threshold setting maintained by the command node from, for example,the external transceiver unit (e.g., as defined by an operator of thetransit vehicle using the external transceiver unit; as defined by alogistics crew member of the transit vehicle using the externaltransceiver unit; or as provided to the external transceiver unit from aremote control center in communication with the external transceiverunit). Another embodiment of method 4300 may have the command nodereceiving a selection update for which of the ID nodes are designated tobe in the group of monitor beacons, where the selection update may bereceived from the external transceiver unit (e.g., as defined by anoperator of the transit vehicle using the external transceiver unit; asdefined by a logistics crew member of the transit vehicle using theexternal transceiver unit; or as provided to the external transceiverunit from a remote control center in communication with the externaltransceiver unit).

Enhanced Container for Environmental Anomaly Monitoring

Further detailed embodiments focus on improved shipping containersystems and apparatus that have sensor-based ID nodes attached to (e.g.,permanently or removably), affixed to, installed on, or integrated aspart of the shipping container. Using such sensor-based ID nodesdisposed on or as part of the different parts of the shipping containeralong with a command node mounted to (e.g., permanently or removably) orintegrated as part of the shipping container, these further embodimentsprovide a container-centric base-level apparatus and system forsensor-based detecting an environmental anomaly related to thecontainer. Such further embodiments may also include enhancedcommunication interfaces that take advantage of low power, improvedrange communication formats. For example, the communication interfacesdeployed on exemplary sensor-based ID nodes and/or an exemplary commandnode may use LPWAN (Low Power Wide Area Network) connectivity, such asLTE 5G, LTE-M, and NB-IOT (NarrowBand IoT). LPWAN, also commonlyreferred to low-power wide-area (LPWA) network or just low-power network(LPN), is a type of wide-area network wireless communication format thatallows for extended range, low-bandwidth communications for powersensitive application, such as with devices that are battery powereddevices (e.g., ID nodes, mobile master nodes, container nodes, commandnodes, and the like). Exemplary types of LPWAN may includeultra-narrowband (UNB) technology from Sigfox, random phase multipleaccess (RPMA) technology from Ingenu, and other long-range WAN protocol(LoRaWAN) technology as promoted by the LoRa Alliance of companies(e.g., IBM, MicroChip, Cisco, Semtech, Singtel, KPN, Bouygues Telecom).LTE-M is a communication technology that allows a node-based device(such as a sensor-based ID node or command node) to directly connect toa Long Term Evolution (4G) cellular network without a gateway and onbatteries. NB-IOT is a low-power communication technology that applies anarrowband approach to cellular IoT (Internet of Things) communicationsallowing for usage of parts of the GSM spectrum bandwidth in unused 200kHz bands.

FIG. 44 is a diagram of an exemplary enhanced shipping container thatcan transport packages and self-monitors for an environmental anomalyusing sensor-based ID nodes disposed within in accordance with anembodiment of the invention. Referring now to FIG. 44, exemplary system44000 is shown with exemplary transit vehicle 24200 and its transitvehicle storage 24205 along with an external transceiver 24150 and firesuppression system 25010 as described in embodiments above (e.g.,similar to that shown in FIG. 41A with exemplary system 41000). System44000 further includes exemplary enhanced shipping container 24300 a,which has command node 24160 mounted to it as well as ID nodes 1-10(24120 a-24120 j, respectively) disposed within container 24300 a.

As shown in FIG. 44, the exemplary shipping container 24300 a has a base41005, a plurality of walls 41010 coupled to the base 41005, a ceiling41015 coupled to the walls 41010 so as to enclose the walls 41010 andbase 41005. In other words, the walls 41010 and ceiling 41015 coupled towalls 41010 are a type of enclosing structure that is coupled to thebase 41005. As coupled to the base 41005, they collectively define aninterior storage space within the shipping container 24300 a that maymaintain packages for transport on the transit vehicle 24200. Exemplaryshipping container 24300 a, as shown in FIG. 44, further illustrates aselectively securable door 44005 hinged to one of the walls 41010 thatprovides securable access into the interior storage space of theshipping container.

ID nodes 1-10 (24120 a-24120 j) are sensor-based ID nodes disposedwithin container 24300 a, as shown in FIG. 44, and are located indifferent locations along the interior of the shipping container 24300a. In more detail, ID nodes 1-2 are each disposed at different locationsas part of ceiling 41015; ID nodes 3-6 are each disposed at differentlocations as part of floor/base 41005; and ID nodes 7, 9, and 10 areeach disposed at different locations as part of walls 41010. ID node 8,as shown in FIG. 44, is disposed on or as part of the door 44005 (whichmay be considered part of the wall when secured in place). As disposedor installed on these different locations within the shipping container24300 a, each of the sensor-based ID nodes may be removablely attached,permanently affixed, or integrated as part of the different parts of theshipping container. For example, when an embodiment replaceably attachessome or all of the ID nodes within shipping container 24300 a, thosereplaceably attached sensor-based ID nodes may be removed and replacedto allow for periodic replacement (e.g., swapping out ID nodes that needcharging, repair, or replacement) with the same type of sensor-based IDnode or with a different ID node having batteries that have a longercharge life, having longer range or different communication capabilities(e.g., use a longer range communicating format to better communicatewith command node 24160), or having specialized sensors (e.g., an IDnode used for monitoring special and/or hazardous items being shippedwithin the container where the sensors on the ID node may correspond toparticular risks associated with such items, correspond to temperatureor other environmental conditions critical for monitoring such items,and the like).

Each of ID nodes 1-10 shown in FIG. 44 are implemented as sensor-basedID nodes having at least an ID node processing unit (also called aprocessor, such as ID node processor 300), an ID node memory coupled tothe processor (e.g., memory 315, 320), at least one environmental sensoroperatively coupled to the processor (e.g., sensors 360), and a wirelessradio transceiver also operatively coupled to the processor (e.g.,communication interface 375). The ID node memory on each sensor-based IDnode in FIG. 44 maintains an ID node monitoring program (e.g., as partof the node control and management code 325). Essentially, the ID nodemonitoring program, when executed on a respective sensor-based ID node,programmatically configures the ID node processor to receive sensor datafrom the environmental sensor and cause the sensor data to be broadcastvia the wireless radio transceiver. In other words, the wireless radiotransceiver is configured (via the operation of the ID node monitoringprogram and interaction of the ID node processing unit with the wirelessradio transceiver) to effectively access the sensor data generated bythe environmental sensor(s) and broadcast the sensor data in response toa report command from the ID node processing unit when the ID nodeprocessing unit executes the ID node monitoring program code.

Exemplary command node 24160 shown in FIG. 44 is mounted (temporarily orpermanently) to shipping container 24300 a. As such, command node 24160includes at least a command node processing unit (e.g., processor26400), a command node memory (e.g., 26415, 26420) coupled to thecommand node processor and that maintains a command node containermanagement program code (e.g., as part of the CN control and managementcode 26425), and two communications interfaces. The first communicationinterface is coupled to the command node processor, and is configured tocommunicate with each of the sensor-based ID nodes using a firstwireless communication format compatible with the wireless radiotransceiver on each of the sensor-based ID nodes. The secondcommunication interface is also coupled to the command node processingunit, and is configured to communicate with at least an externaltransceiver unit associated with a transit vehicle transporting theshipping container using a second wireless communications format.

In operation, the command node processing unit of the shippingcontainer's command node is programmatically configured, when executingthe command node container management program code, to be operative todetect the sensor data broadcasted from the sensor-based ID nodes usingthe first communication interface; responsively identify theenvironmental anomaly for the shipping container when the detectedsensor data does not include the sensor data from at least a thresholdnumber of the sensor-based ID nodes, and when the detected sensor dataindicates an environmental condition that exceeds an environmentalthreshold; generate a layered alert notification related to theenvironmental anomaly for the shipping container in response toidentifying the environmental anomaly for the shipping container (wherethe layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority); and then causes the second communicationinterface to transmit the layered alert notification to the transceiverunit to initiate a mediation response related to the targeted mediationaction.

In more detail, the enhanced shipping container 24300 a shown in FIG. 44may use relative sensor data generated and monitored over time. Forexample, each of the sensor-based ID nodes used as part of the enhancedshipping container apparatus is further operative to incrementallygenerate the sensor data over a time period using the environmentalsensor on each of the respective sensor-based ID nodes. As such, thecommand node processing unit of the container's command node is furtherprogrammatically configured to monitor the generated sensor data fromeach of the sensor-based ID nodes over the time period to identifyrelative changes in the generated sensor data over the time period. Thecommand node processor may be programmatically configured to thencompare the identified relative changes in the generated sensor data andcontext data (e.g., context data 26560) locally maintained on thecommand node memory related to those of the sensor-based ID nodes thatare related to the relative changes in the generated sensor data. Suchcontext data in this further embodiment includes at least a relativeenvironmental threshold condition respectively corresponding to theshipping container. The command node processor may be programmaticallyconfigured to then identify the environmental anomaly for the shippingcontainer when the comparison of identified relative changes in thegenerated sensor data and the context data indicates a changedenvironmental condition for the shipping container that exceeds therelative environmental threshold condition.

In a further embodiment of the enhanced shipping container 24300 a, thesensors used on the deployed sensor-based ID nodes within container24300 a may be different types of environmental sensors. For example, anenvironmental sensor for a first of the sensor-based ID nodes may beimplemented with a temperature sensor while the environmental sensor fora second of the sensor-based ID nodes may be implemented with abarometric pressure sensor. As such and in more detail, the command nodeprocessing unit of the container's command node may be furtherprogrammatically configured to responsively identify the environmentalanomaly for the shipping container when (a) the sensor data detectedfrom the first sensor-based ID node is a temperature value; (b) thesensor data detected from the second sensor-based ID node is abarometric pressure value; (c) the temperature value indicates a firstlocal environmental condition proximate the first sensor-based ID nodeexceeds the environmental threshold condition for the shipping containeraccording to first context data locally maintained on the command nodememory related to that first sensor-based ID node (where the firstcontext data includes at least a temperature threshold condition for theshipping container); and (d) the barometric pressure value indicates asecond local environmental condition proximate the second sensor-basedID node exceeds the environmental threshold condition for the shippingcontainer according to second context data locally maintained on thecommand node memory related to that second sensor-based ID node (wherethe second context data includes at least a barometric pressurethreshold condition for the shipping container). In some embodiments,one sensor-based ID node may have an environmental sensor implemented bya temperature sensor while the environmental sensor for anothersensor-based ID node may be implemented with a barometric pressuresensor, a radiation sensor, or a chemical sensor. Further still, theenvironmental sensor for a sensor-based ID node may be implemented withmultiple sensor elements (such as a temperature sensor element and abarometric pressure sensor element).

In another embodiment of the enhanced shipping container, the identifiedenvironmental anomaly may be based on sensor data compared to profiledata maintained on the command node. The profile data, which may bemaintained as a type of context data locally maintained on the commandnode memory (e.g., profile data 430 on memory 26415/26420 of commandnode 26000), may provide a time-based profile of sensor data that isindicative of a particular environmental anomaly. Such a time-baseprofile of temperature data, for example, may indicate a lithium-ionbattery fire for a particularly rapid rise in temperature over time to aparticular range of temperatures within that time frame. Such atemperature profile, as sensed by a temperature sensor, may be used todetect the environmental anomaly as well as the type of environmentalanomaly that can be used by the command node to generate the appropriatealert notification to initiate the appropriate mediation response.Another example may have a pressure profile which, when matched overtime, may indicate an explosion (e.g., a sudden increase in pressure,then followed by a rapid drop in pressure).

A further embodiment where a sensor on the sensor-based ID node is abarometric pressure sensor, the context data reflecting a pressureprofile of pressure values over time that may be detected in aparticular pattern that when matched indicates

In another embodiment of the enhanced shipping container, the identifiedenvironmental anomaly may be based on sensor data from a combination oftemperature information with other types of sensor data. For example andin more detail, the command node processing unit may be furtherprogrammatically configured to responsively identify the environmentalanomaly when: (a) the sensor data detected from the first sensor-basedID node is a temperature value; (b) the sensor data detected from thesecond sensor-based ID node is an environmental condition value ofeither a sensed barometric pressure level by the barometric sensor, adetected radiation level by the radiation sensor, or a detected chemicalby the chemical sensor; (c) the temperature value indicates a firstlocal environmental condition proximate the first sensor-based ID nodeexceeds the environmental threshold condition for the shipping containeraccording to first context data related to the first sensor-based IDnode (where the first context data includes at least a temperaturethreshold condition for the shipping container); and (d) theenvironmental condition value indicates a second local environmentalcondition proximate the second sensor-based ID node exceeds theenvironmental threshold condition for the shipping container accordingto second context data related to the second sensor-based ID node (wherethe second context data includes at least an environmental thresholdcondition for the shipping container corresponding to the type of sensordata detected from the second of the sensor-based ID nodes). In thisexample, the detected chemical may be indicative of an explosive withinthe shipping container, a fire within the shipping container, or may beone of either CO or CO₂ disposed within the shipping container.

In still another embodiment of the enhanced shipping container, theidentified environmental anomaly for the shipping container may, forexample, be a fire within the shipping container when the sensor datafrom the temperature sensor comprises a temperature value exceeding atemperature threshold maintained by the command node in the command nodememory as part of context data for the shipping container and when thesensor data from the barometric pressure sensor is a barometric pressurevalue exceeding a pressure threshold maintained by the command node inthe command node memory as part of the context data for the shippingcontainer. In another example, the identified environmental anomaly forthe shipping container may be an explosion within the shipping containerwhen the sensor data from the temperature sensor is a temperature valueexceeding a temperature threshold maintained by the command node in thecommand node memory as part of context data for the shipping containerand when the sensor data from the barometric pressure sensor is abarometric pressure value that is below a pressure threshold maintainedby the command node in the command node memory as part of the contextdata for the shipping container. In still another example, theidentified environmental anomaly for the shipping container comprises anexplosion within the shipping container when the sensor data from thetemperature sensor is a temperature value exceeding a temperaturethreshold maintained by the command node in the command node memory aspart of context data for the shipping container and when the sensor datafrom the barometric pressure sensor is a barometric pressure value dropsfaster than a pressure drop threshold maintained by the command node inthe command node memory as part of the context data for the shippingcontainer. In an additional example, the identified environmentalanomaly for the shipping container may be a detected chemical-relatedfire and/or a detected chemical that is related to a fire within theshipping container when the sensor data from the temperature sensor is atemperature value exceeding a temperature threshold maintained by thecommand node in the command node memory as part of context data for theshipping container and when the sensor data from the chemical sensormatches a predetermined chemical profile maintained by the command nodein the command node memory as part of the context data for the shippingcontainer. In a further example, the identified environmental anomalyfor the shipping container may be a radiation leak within the shippingcontainer when the sensor data from the temperature sensor is atemperature value exceeding a temperature threshold maintained by thecommand node in the command node memory as part of context data for theshipping container and when the sensor data from the radiation sensormatches a predetermined radiation profile maintained by the command nodein the command node memory as part of the context data for the shippingcontainer. As such, sensor information as well as context data(including profile information on what may be stored within the shippingcontainer) may be leveraged to allow the enhanced shipping container tobetter and more precisely identify the particular environmental anomaly.

When detecting sensor data broadcasted by the different sensor-based IDnodes, the container's command node may set or adjust how often thatsensor data is broadcast. For example, the command node processing unitof the command node may be further operative to detect the sensor databroadcasted from the sensor-based ID nodes by being operative to (a)detect the sensor data broadcasted by the sensor-based ID nodesaccording to a broadcast profile maintained by each of the sensor-basedID nodes (where the broadcast profile (e.g., part of profile data 430 oncommand node 24160) defines a first messaging rate used to regulate howoften the generated sensor data is transmitted to the command node suchthat the first messaging rate is higher than a default messaging rate);and (b) cause the first communication interface to instruct each of thesensor-based ID nodes to broadcast future generated sensor data at asecond messaging rate that is higher/faster than the first messagingrate after causing the second communication interface to transmit thelayered alert notification to the transceiver unit. Further, the commandnode processing unit of the command node may also cause the firstcommunication interface to instruct each of the sensor-based ID nodes tochange from the default messaging rate to the first messaging rate,which may be established or set as an initial value correlated to anenvironmental risk associated with material maintained within theshipping container.

When the enhanced shipping container's command node generates thelayered alert notification, further embodiments may implement thisfunctionality in more detail with respect to how to select the targetedmediation recipient. For example, the container's command node may befurther programmatically configured to automatically select the targetedmediation recipient based upon at least one of (a) how many of thesensor-based ID nodes were not detected above the threshold number ofthe sensor-based ID nodes and (b) how much the environmental conditionexceeds the environmental threshold. As such, the targeted mediationrecipient identified by the command node in the layered alertnotification may be a triggered fire suppression apparatus (e.g.,exemplary onboard triggered fire suppression system 25010 as shown inFIG. 44 and explained in more detail with reference to FIGS. 32A-32C) onthe transit vehicle that is operative to automatically respond to thedetected environmental anomaly based upon receipt of the layered alertnotification. Another targeted mediation recipient that may beidentified by the command node in the layered alert notification is anoperator of the transit vehicle that can alter movement of the transitvehicle. Further, still another targeted mediation recipient identifiedby the command node in the layered alert notification may be a logisticscrew member of the transit vehicle that can inspect the shippingcontainer.

When the enhanced shipping container's command node generates thelayered alert notification, further embodiments may implement thisfunctionality in more detail with respect to how to select theparticular targeted mediation action that is initiated in response tothe detected environmental anomaly in the shipping container. Forexample, the container's command node may be further programmaticallyconfigured to automatically select the targeted mediation action basedupon at least one of (a) how many of the sensor-based ID nodes were notdetected above the threshold number of the sensor-based ID nodes and (b)how much the environmental condition exceeds the environmentalthreshold. In more detail, the targeted mediation action identified bythe command node in the layered alert notification depends upon what isloaded within the shipping container as indicated by the shippinginformation maintained on the command node memory.

The targeted mediation action may also depend on further information,such as vehicle status data (indicating a status of the transit vehicletransporting the enhanced shipping container) and/or container statusdata. For example, the enhanced shipping container's command nodeprocessing unit may be further programmatically configured to receivevehicle status data from the external transceiver unit of the transitvehicle using the second communication interface and maintain thevehicle status data in the command node memory. With the vehicle statusdata, the targeted mediation action identified in the layered alertnotification may depend upon a state of the transit vehicle as indicatedby the vehicle status data. Examples of such a state of the transitvehicle may include a takeoff vehicular status, a cruising vehicularstatus, a landing vehicular status, or an on-the-ground vehicularstatus. As such, when the transit vehicle is in the state of beingon-the-ground, the command node is automatically equipped withinformation to more quickly and safely identify the targeted mediationaction (e.g., inspect the shipping container) that may be different thana targeted mediation action identified when the transit vehicle is in acruising statue (e.g., change course to stop or land the vehicle). Assuch, safety advantages abound for the transit vehicle, personnelinvolved with the transit vehicle, as well as property being transportedby the transit vehicle.

In another example, the command node memory may maintain containerstatus data corresponding to the shipping container. With this containerstatus data, the targeted mediation action in the command node generatedlayered alert notification may depend upon a state of the shippingcontainer as indicated in the container status data maintained on thecommand node memory.

Information on the location of the shipping container within the transitvehicle may also be leveraged by the enhanced shipping container'scommand node to better identify a targeted mediation action. Forexample, the enhanced shipping container's command node may furtherinclude location circuitry (similar to location circuitry 475 used on amaster node) coupled to the command node processing unit, where thecommand node's location circuitry detects geolocation data related to acurrent location of the shipping container within the transit vehicle.With such geolocation data, the targeted mediation action in the commandnode generated layered alert notification may depend upon the currentlocation of the shipping container as indicated in the geolocation data.For example, the identified targeted mediation action may include aninspection of the shipping container if the container is located incertain spots on the transit vehicle, but may include an automatedimmediate activation of an onboard fires suppression system when thecontainer is located near particular parts of the transit vehicle deemedmore critical than others (e.g., a fuel supply, an oxygen system, andthe like).

Loading plan data may also be used by the enhanced shipping container'scommand node when identifying an appropriate targeted mediationresponse. For example, the command node memory may maintain loading plandata indicating the relative location of the shipping container withinthe transit vehicle. With such loading plan data, the targeted mediationaction identified by the command node in the layered alert notificationmay depend upon the relative location of the shipping container withinthe transit vehicle as indicated in the loading plan data.

Likewise, facility status data associated with a storage facility forthe enhanced shipping container may also be used when identifying anappropriate targeted mediation response. In more detail, the targetedmediation action identified by the command node in the layered alertnotification may depends upon a state of the storage facility asindicated in the facility status data maintained within the command nodememory.

In further embodiments, the command node processing unit may establishthe mediation response priority (as part of the layered alertnotification) in more detail. For example, the enhanced shippingcontainer's command node may be further programmatically configured toautomatically establish the mediation response priority based upon atleast one of (a) how many of the sensor-based ID nodes were not detectedabove the threshold number of the sensor-based ID nodes and (b) how muchthe environmental condition exceeds the environmental threshold. Assuch, the mediation response priority may be established by the commandnode as a high priority level indicating further travel by the transitvehicle is to be at least minimized as part of the mediation response,or an intermediate priority level indicating further travel by thetransit vehicle is permissible as part of the mediation response.

In still further embodiments of an enhanced shipping container apparatusas noted above, the command node processing unit may take further stepsto verify or validate the sensor data received so as to address thepotential for spoofing of sensor data or taking mediation responsiveactions unnecessarily. For example, the command node processing unit maydetect the sensor data using the first communication interface by beingoperative to (a) receive the sensor data broadcasted from a firstsensor-based ID node using the first communication interface; (b)confirm the validity of the received sensor data; (c) repeat (a) and (b)for the remainder of the sensor data received from any of the remainingsensor-based ID nodes using the first communication interface; and (d)selectively compile the detected sensor data using only the receivedsensor data confirmed valid. In a further example, the command nodeprocessor may confirm the validity of the received sensor data in an“active” manner by being further operative to cause the firstcommunication interface to send an authentication request to the firstsensor-based ID node, and receive a validation response from that firstsensor-based ID node via the first communication interface. Such avalidation response may authenticate the sensor data broadcasted fromthe particular sensor-based ID node. In another example, the commandnode processor may confirm the validity of the received sensor data in a“passive” manner by being further operative to access a validationsequence for the first sensor-based ID node (where the validationsequence is maintained in the command node memory and characterizesexpected broadcasts from that particular sensor-based ID node) anddetermine if the received sensor data from the first sensor-based IDnode matches a predetermined one of the expected broadcasts from thatsensor-based ID node according to the validation sequence stored withinthe command node memory. Such a predetermined one of the expectedbroadcasts may be a rotating value previously received by the commandnode for the first sensor-based ID node.

In still further embodiments of this enhanced shipping containerapparatus, as shown in FIG. 44, the communication interface on thecommand node to communicate outside the shipping container may beenhanced with more long range, low power technology, such as a low powerwide area network (LPWAN) interface operative to communicate as thesecond wireless communications interface format. In more detail, such asecond communication interface format may be implemented as a narrowband Internet of Things (NB-IoT) format, or a long term evolution (LTE)category M1 format.

While the enhanced shipping container apparatus embodiments describedabove generates the layered alert notification and transmits thatnotification to an external transceiver to initiate the mediationresponse, another embodiment of such an enhanced shipping containerapparatus is described below where the sensor-based ID nodes and thecommand node are explicitly types of replaceable wireless networkelements that may be removed and replaced as line replaceable modulesfor the enhanced shipping container apparatus. In this way, such furtherembodiments of the enhanced shipping container apparatus may bere-configured to handle and effectively self-monitor different types ofpackages being transported within the interior storage apparatus'shipping container for an environmental anomaly.

In more detail, this other embodiment of an enhanced shipping containerapparatus includes at least a shipping container housing, multiplesensor-based ID nodes removably attached to different parts of theshipping container housing, and a command node removably mounted to theshipping container housing. The shipping container housing (e.g.,exemplary shipping container 24300 a as shown in FIG. 44), in thisembodiment, has at least a base portion (e.g., base 41005), and anenclosing structure (e.g., walls 41010, ceiling 41015, and door 44005)that is coupled to the base portion and that defines an interior storagespace within the shipping container housing. The sensor-based ID nodesare removably attached to different parts of the shipping containerhousing, such as to the base, walls, door, and/or ceiling. Each of thesensor-based ID nodes are a first type of replaceable wireless networkelements deployed on the shipping container (e.g., a sensor-equipped IDnode wireless network element, such as exemplary ID node 120 a as shownin FIG. 3 or exemplary sensor-based ID nodes as shown in FIG. 44).Consistent with the description of such exemplary sensor-based ID nodes,each has at least an ID node enclosure for housing one or morecomponents of the ID node, an ID node processing unit disposed withinthe ID node enclosure; an ID node memory coupled to the ID nodeprocessing unit and maintaining at least an ID node monitoring programcode; at least one environmental sensor operatively coupled to the IDnode processing unit and configured to generate sensor data related toan environmental condition proximate the respective sensor-based IDnode; and a wireless radio transceiver coupled to the ID node processingunit. The sensor-based ID node's wireless radio transceiver isconfigured to access the sensor data generated by the environmentalsensor and broadcast the sensor data in response to a report commandfrom the ID node processing unit when the ID node processing unitexecutes the ID node monitoring program code.

The ID node enclosure for each of the sensor-based ID nodes may beimplemented to house all or a portion of the components of thesensor-based ID node. For example, the ID node processor, memory, andwireless radio transceiver may be fixed relative to the ID nodeenclosure and disposed within the enclosure, while one or more of theenvironmental sensors may be operatively coupled to the processor and bedisposed so as to have sufficient exposure to the environment outside ofthe ID node enclosure for sensing such an environment. Those skilled inthe art will further appreciate that exemplary environmental sensorsused with a sensor-based ID node may be remote from the ID nodeenclosure—e.g., one or more sensors that have connections back to the IDnode processor but that are disposed external to the ID node enclosurein one or more locations near the sensor-based ID node's enclosure. Inthis manner, a sensor-based ID node may deploy an array of similar ordifferent types of environmental sensors that may be disposed in, on, orexternal to the ID node enclosure while each sensor is still operativelycoupled to the ID node processor.

Such an ID node enclosure may be sized to fit within recessed sectionsof the shipping container housing in some embodiments. As such, asensor-based ID node may be removably attached to a particular part ofthe shipping container housing within such a recessed section of theshipping container house so as to not protrude from the interior surfaceof the shipping container housing. Those skilled in the art willappreciate that the command node may similarly be removably disposed ormounted within a recessed section of the shipping container housing. Theshipping container housing may further include securing straps, pockets,clamps, restraining hardware, screws, bolts, or other fasteners that maybe used to hold the sensor-based ID node/command node in place relativeto the shipping container housing.

The command node is removably mounted to the shipping container as asecond type of replaceable wireless network element deployed on theshipping container (e.g., an exemplary command node wireless networkelement, such as exemplary command node 26000 as shown in FIG. 26 orexemplary command node 24160 as shown in at least FIG. 44). Consistentwith the description of such an exemplary command node, the command nodein this embodiment has at least a command node processing unit; acommand node memory coupled to the command node processing unit andmaintaining at least command node container management program code; andtwo different communications interfaces coupled to the command nodeprocessing unit. A first of the communication interfaces is configuredto communicate with each of the sensor-based ID nodes using a firstwireless communication format compatible with the wireless radiotransceiver on each of the sensor-based ID nodes, while a second of thecommunication interfaces is operative to communicate outside theshipping container housing using a second wireless communicationsformat.

In operation, the command node processing unit of the apparatus'scommand node is programmatically configured, when executing the commandnode container management program code, to be operative to detect thesensor data broadcasted from the sensor-based ID nodes using the firstcommunication interface; responsively identify the environmental anomalyfor the shipping container when the detected sensor data does notinclude the sensor data from at least a threshold number of thesensor-based ID nodes and when the detected sensor data indicates anenvironmental condition that exceeds an environmental threshold;generate a layered alert notification related to the environmentalanomaly for the shipping container in response to identifying theenvironmental anomaly for the shipping container, wherein the layeredalert notification identifies a targeted mediation recipient, identifiesa targeted mediation action, and establishes a mediation responsepriority; and cause the second communication interface to broadcast alayered alert notification that initiates a mediation response relatedto the targeted mediation action.

Further variations of this embodiment of an enhanced shipping containerapparatus (i.e., the embodiment having sensor-based ID nodes and acommand node as replaceable wireless network elements that areexplicitly removable and replaceable as line replaceable modules) may beimplemented with the same enhancements, details, and variations of thepreviously described embodiment of an enhanced shipping containerapparatus.

Coordinated Response when Monitoring for Environmental Anomaly

Further embodiments provide a level of redundancy by deploying one ormore backup types of command nodes. When monitoring wireless ID nodeswithin a shipping container, the use of such backup types of commandnodes provides further robust decision points that can take over for aprimary command node monitoring for an environmental anomaly related toa shipping container. Given an anticipated hostile or hazardousenvironment within a shipping container when and where an environmentalanomaly may occur (e.g., a fire, explosion, chemical leak, radiationleak, and the like), deploying backup types of command nodes asadditional types of networked wireless nodes serves to enhance systemsand methods that monitor the shipping container to detect anenvironmental anomaly. In other words, enhancing and improving suchmonitoring and detection embodiments with redundant command nodes forthe shipping container allows a system or method to more robustly handledetection, reporting, and initiating of mediation responses related tosuch environmental anomalies with the shipping container.

In general, exemplary types of backup command nodes may include adesignated survivor command node mounted to the shipping container thatmay take over the monitoring, detecting, and responsive notification andmediation response initiation activities from a primary command nodeonce that primary command node has become inoperative (e.g., once thedesignated survivor command node detects that the primary command nodehas become inoperative). Another type of backup command node may come inthe form of one from multiple possible survivor command nodes where eachmay be deployed in different parts of the shipping container so as tospread the risk of where an intense environmental anomaly may erupt thatmay render a wireless node inoperative in that vicinity. As such, whenthe primary command node has become inoperative (e.g., is no longer in anormal operating state), one of the possible survivor command nodes maybe selected (e.g., based upon a priority rank associated with eachpossible survivor command node) to quickly and responsively take over soas to operate as the designated survivor command node performing theprimary command node's container monitoring operations given detectionthat the primary command node is no longer operative.

FIGS. 45A-45B are diagrams of an exemplary adaptive wireless nodenetwork system for monitoring a shipping container for an environmentalanomaly using an exemplary primary command node and an exemplarydesignated survivor command node in accordance with an embodiment of theinvention. Referring now to FIG. 45A, exemplary system 45000 is shownwith exemplary transit vehicle 24200 and its transit vehicle storage24205 along with an external transceiver 24150 and fire suppressionsystem 25010 as described in embodiments above (e.g., similar to thatshown in FIG. 41A with exemplary system 41000). System 44000 furtherincludes exemplary shipping container 24300 a as configured to include aprimary command node 24160 mounted to it, a designated survivor commandnode 45160 mounted to it, as well as ID nodes 1-8 (24120 a-24120 h,respectively) as shown disposed within container 24300 a.

ID nodes 1-8 shown in FIGS. 45A-46B (24120 a-24120 h) are a group ofwireless ID nodes disposed within container 24300 a, and are disposedwithin the shipping container 24300 a. Each of ID nodes 1-8 areoperative to broadcast one or more wireless signals via a wireless radiotransceiver, where those wireless signals represent ongoing signalactivity from that respective ID node (i.e., indicating normal operationof the ID node). While each of ID nodes 1-8, as shown in FIGS. 45A-46B,are not illustrated as being associated with particular objects (such aspackages), those skilled in the art will appreciate that any or all ofID nodes 1-8 may be associated with one or more objects beingtransported in the shipping container 24300 a (e.g., similar to theexample shown in FIG. 24B where exemplary ID nodes are disposed withinparticular packages being transported in shipping container 24300). Assuch, each of the wireless ID nodes 1-8 may be removablely attached,permanently affixed, or integrated as part of the different parts of theshipping container in a particular example. Further, in another example,each of the wireless ID nodes 1-8 may be associated with, travel with,attached to (removably or permanently) an object (such as a package)being transported within the shipping container 24300 a.

Each of ID nodes 1-8 shown in FIGS. 45A-46B may further be implementedas sensor-based wireless ID nodes having at least an ID node processingunit (also called a processor, such as ID node processor 300), an IDnode memory coupled to the processor (e.g., memory 315, 320), at leastone environmental sensor operatively coupled to the processor (e.g.,sensors 360), and a wireless radio transceiver also operatively coupledto the processor (e.g., communication interface 375). The ID node memoryon each sensor-based ID node in FIG. 44 maintains an ID node monitoringprogram (e.g., as part of the node control and management code 325).Essentially, the ID node monitoring program, when executed on arespective sensor-based ID node, programmatically configures the ID nodeprocessor to receive sensor data from the environmental sensor and causethe sensor data to be broadcast via the wireless radio transceiver. Inother words, the wireless radio transceiver is configured (via theoperation of the ID node monitoring program and interaction of the IDnode processing unit with the wireless radio transceiver) to effectivelyaccess the sensor data generated by the environmental sensor(s) andbroadcast the sensor data in response to a report command from the IDnode processing unit when the ID node processing unit executes the IDnode monitoring program code.

Exemplary primary command node 24160 shown in FIGS. 45A-46B is disposed(temporarily, removably, or permanently) within shipping container 24300a at, for example, a predetermined location within the container, on apredetermined location of the container, or associated with a particularpackage or object within the container. As such, command node 24160includes at least a command node processing unit (e.g., processor26400), a command node memory (e.g., 26415, 26420) coupled to thecommand node processor and that maintains a command node containermanagement program code (e.g., as part of the CN control and managementcode 26425 and that implements a primary container monitoringoperation), and two communications interfaces. The first communicationinterface is coupled to the command node processor, and is configured tocommunicate with each of the wireless ID nodes 1-8 using a firstwireless communication format compatible with the wireless radiotransceiver on each of the wireless ID nodes 1-8. The secondcommunication interface is also coupled to the command node processingunit, and is configured to communicate with at least an externaltransceiver unit (e.g., exemplary transceiver 24150 or a transceiver32010 component of fire suppression system 25010) associated with atransit vehicle transporting the shipping container using a secondwireless communications format.

In its normal operating state, the command node processing unit ofprimary command node 24160 is programmatically configured, whenexecuting the command node container management program code(implementing executable instructions that carry out the primarycontainer monitoring operation as set forth below), to be operative tomonitor signal activity from the ID nodes 1-8; responsively identify theenvironmental anomaly based upon the monitored signal activity from theID nodes; generate a layered alert notification related to theenvironmental anomaly for the shipping container in response toidentifying the environmental anomaly for the shipping container (wherethe layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority); and transmits the layered alertnotification to the external transceiver (via the second communicationinterface on primary command node 24160) to initiate a mediationresponse related to the targeted mediation action.

In more detail, the identified targeted mediation recipient may be atriggered fire suppression apparatus on the transit vehicle thatsupplies a fire suppression agent into the shipping container as themediation response, or personnel related to operations of the transitvehicle that are prompted by the external transceiver as the mediationresponse. Additionally, the targeted mediation action identified by theprimary command node in the layered alert notification may be identifiedbased upon an extent of an observed drop in the monitored signalactivity from the ID nodes and what is loaded within the shippingcontainer as indicated by shipping information maintained on the primarycommand node. Further still, the mediation response priority establishedby the primary command node in the layered alert notification may beestablished based upon an extent of an observed drop in the monitoredsignal activity from the ID nodes, where the extent of the observed dropreflects a priority level for the mediation response priority thatindicates one type of permissive status condition for further travel bythe transit vehicle.

In more detail and as part of this exemplary primary containermonitoring operation, primary command node 24160 may monitor signalactivity from the wireless ID nodes 1-8 by detecting sensor databroadcast from each of the ID nodes. As such, primary command node 24160may be further configured to responsively identify the environmentalanomaly for the shipping container when, for example, the detectedsensor data does not include the sensor data from at least a thresholdnumber of the ID nodes or when the detected sensor data indicates anenvironmental condition that exceeds an environmental threshold. Theenvironmental condition and the environmental threshold may, forexample, be related to detected temperature, detected pressure, detectedradiation, or the detected presence of a particular chemical (e.g., whenthe detected chemical presence is indicative of an explosive within theshipping container or a fire within the shipping container).

Additionally, the primary command node may detect the sensor databroadcasted from the ID nodes according to a broadcast profilemaintained by each of the ID nodes. Such a broadcast profile may definea first messaging rate used by the particular ID node to regulate howoften the generated sensor data is broadcast, where the first messagingrate is higher than a default messaging rate. As such, the primarycommand node may instruct each of the ID nodes to change from thedefault messaging rate to the first messaging rate. The primary commandnode may also, in some embodiments, instruct each of the ID nodes tobroadcast future generated sensor data at a second messaging rate thatexceeds the first messaging rate after the primary command nodetransmits the layered alert notification to the external transceiverassociated with the transit vehicle as part of the primary containermonitoring operation. In a more detailed embodiment, the first messagingrate for the ID nodes may be an initial value correlated to anenvironmental risk associated with material maintained within theshipping container.

As part of this adaptive system 45000, and embodiment may have exemplarydesignated survivor command node 45160 within the shipping container24300 a. Further embodiments may have designated survivor command node45160 being disposed (temporarily, removably, or permanently) withinshipping container 24300 a at, for example, a predetermined locationwithin the container, on a predetermined location of the container, orassociated with a particular package or object within the container. Asshown in FIGS. 45A-45B, designated survivor command node 45160 is acontainer node mounted to the shipping container 24300 a and operativeto also directly communicate with the ID nodes 1-8 disposed internal tothe shipping container and to directly communicate with the externaltransceiver associated with the transit vehicle.

Typically, exemplary designated survivor command node 45160 may bedisposed remotely within shipping container 24300 a with respect to theposition of the primary command node 24160 (e.g., on opposing sides ofthe shipping container relative to each other) so as to increase thechance that any environmental anomaly within shipping container 24300 athat renders primary command node 24160 to be inoperative (e.g., out ofits normal operating state of conducting the primary containermonitoring operation set forth above), will still have designatedsurvivor command node 45160 being operative and able to take over theprimary container monitoring operation from the now inoperative primarycommand node 24160. In other words, designated survivor command node45160 is configured to communicate with the primary command node 24160,as shown in FIG. 45A, and operate as the primary command node when thedesignated survivor command node 45160 is unable to communicate with theprimary command node 24160, as shown in FIG. 45B where primary commandnode 24160 is no longer operative or able to communicate with designatedsurvivor command node 45160 (e.g., because of damage to primary commandnode 24160 from an environmental anomaly or another malfunction in theprimary command node 24160).

For example, the system's designated survivor command node 45160 mayperiodically communicate with primary command node 24160 to ensurenormal operation (as shown in FIG. 45A), but initiate taking over as theprimary command node (e.g., conducting the primary container monitoringoperation as shown in FIG. 45B) when the primary command node 24160ceases to respond, such as when the designated survivor command node45160 fails to receive a response from the primary command node 24160within a threshold reporting interval. In another example, the primarycommand node 24160 may, as part of the primary container monitoringoperation, periodically send a status message to the designated survivorcommand node 45160 without prompting so that when the designatedsurvivor command node 45160 fails to receive a timely and expectedstatus message from the primary command node 24160, the designatedsurvivor command node 45160 responsively takes over for the primarycommand node 24160 as described.

In still another example, the designated survivor command node may notwait for the primary command node to become inoperative orincommunicative before taking on the functionality and responsibility ofthe primary command node. Instead, the designated survivor command node45160 may be monitoring the ID nodes for signal activity and thenpreemptively coordinate with the primary command node 24160 so as totake over the primary container monitoring operation from the primarycommand node 24160 when the monitored signal activity from the ID nodes1-8 indicates less than a threshold number of the ID nodes arebroadcasting.

In a further embodiment, the adaptive system may use one of multipleprioritized survivor command nodes disposed within the shippingcontainer as the system's designated survivor command node, which takesover from the primary command node when the primary command node isrendered inoperative and uncommunicative. FIGS. 46A-46B are diagrams ofan exemplary adaptive wireless node network system for monitoring ashipping container for an environmental anomaly using a primary commandnode and one of multiple prioritized survivor command nodes used as thedesignated survivor command node in accordance with an embodiment of theinvention. Referring now to FIG. 46A, exemplary system 46000 is shownlargely the same as that shown with system 45000 in FIG. 45A, but nowincluding two prioritized survivor command nodes 46160 a, 46160 b shownin FIG. 46A instead of the lone designated survivor command node 45160shown in FIG. 45A. As such, the designated survivor command node asdescribed as part of an adaptive system may be implemented by one theprioritized survivor command nodes 46160 a, 46160 b associated with theprimary command node 24160 shown in FIG. 46A. Each of the prioritizedsurvivor command nodes 46160 a, 46160 b may be implemented as acontainer node operative to directly communicate with the ID nodes 1-8disposed internal to the shipping container 24300 a as well as todirectly communicate with the external transceiver 24150 (or thetransceiver implemented as part of fire suppression system 25010)associated with the transit vehicle. Each of the prioritized survivorcommand nodes 461060 a, 46160 b is disposed within the shippingcontainer 24300 a (e.g., disposed within the shipping container atdifferent physical locations within the shipping container, such ashaving a first prioritized survivor command node 46160 a disposed on theceiling 41015 of container 24300 a while a second prioritized survivorcommand node 46160 b is disposed on the base 41005 of the container24300 a). Each of the prioritized survivor command nodes 46160 a, 46160b also has a priority rank (e.g., data that is part of CN control andmanagement code 26425) used to determine which of these node will takethe place of the inoperative primary command node as the designatedsurvivor command node. The respective priority rank of each of theprioritized survivor command nodes may be related to their respectivedistance from the primary command node—i.e., the closer the particularprioritized survivor command node is to the primary command node, thelower the rank that particular prioritized survivor command node has. Inother words, a highly ranked prioritized survivor command node may be agreater distance from the primary command node than others of theprioritized survivor command nodes.

As such, each of prioritized survivor command nodes 46160 a, 46160 b isconfigured to communicate with the primary command node 24160 and othersof the prioritized survivor command nodes (as reflected in FIG. 46A) andto selectively operate as the primary command node 24160 when higherpriority ranked ones of the prioritized survivor command nodes 46160 a,46160 b are unable to communicate with the primary command node 24160.For example,

For example, each of the system's prioritized survivor command nodes46160 a, 46160 b may periodically communicate with primary command node24160 to ensure normal operation. When the primary command node 24160ceases to respond (e.g., no response within a threshold reportinginterval), the higher priority ranked one of prioritized survivorcommand nodes 46160 a, 46160 b initiates taking over within the adaptivemonitoring system as the primary command node (e.g., conducting theprimary container monitoring operation). In another example, the primarycommand node 24160 may, as part of the primary container monitoringoperation, periodically send a status message to each of the prioritizedsurvivor command nodes 46160 a, 46160 b without prompting so that whenthe prioritized survivor command nodes fail to receive a timely statusmessage from the primary command node 24160, the prioritized survivorcommander node with the higher priority ranking take over for theprimary command node 24160 as described. The determination of which ofthe multiple prioritized survivor command nodes has the highest priorityranking (and is still functional to take on the operation of the primarycommand node), the prioritized survivor commands 46160 a, 46160 b maycommunicate with each other to compare priority rankings. This may beimplemented as a collective request sent between the multipleprioritized survivor command nodes, once the primary command node isdetermined not to be responsive or to be in operative (e.g., no responsewithin the threshold reporting interval). Each of the prioritizedsurvivor command nodes that remain functional (as some may be damagedand in operative as the primary command node is) responds to the othersof the prioritized survivor command nodes with its respective priorityranking so that only the one with the highest priority ranking of thoseprioritized survivor command nodes left operating may be the designatedsurvivor command node that takes over the functionality of conductingthe primary container monitoring operation as was being performed by theprimary command node. As such, those skilled in the art can appreciatethat further failure handoffs may take place with others of theprioritized survivor command nodes taking over the functionality ofconducting the primary container monitoring operations when theprioritized survivor command node operating as the designated survivorcommand node is also rendered inoperative and uncommunicative. As such,an embodiment of such an adaptive monitoring system may use “layers” ofredundant types of command nodes to continue the primary containermonitoring operations.

The above-described adaptive monitoring system embodiments may also beused to implement embodiments of an improved method for adaptivelymonitoring a shipping container for an environmental anomaly. FIG. 47 isa hybrid flow diagram illustrating an exemplary method for adaptivelymonitoring a shipping container for an environmental anomaly using aprimary command node and a designated survivor command node that dependsupon the operating state of the primary command node in accordance withan embodiment of the invention. As shown in FIG. 47, exemplary method4700 is an improved method for adaptively monitoring a shippingcontainer (e.g., shipping container 24300 a) for an environmentalanomaly using elements of wireless node network having at least a groupof wireless ID nodes (e.g., ID nodes 1-8 as shown in FIGS. 45A-46B)disposed within the shipping container, a primary command node (e.g.,primary command node 24160) disposed within the shipping container and adesignated survivor command node (e.g., designed survivor command node)mounted to the shipping container.

Referring now to FIG. 47, exemplary method 4700 begins at step 4705 witheach in the group of the wireless ID nodes broadcasting a series ofwireless signals representing signal activity by each in the group ofthe wireless ID nodes. The series of wireless signals need not beperiodic, but generally includes multiple signals over time that may bedetected by another node, such as the primary command node 24160 anddesigned survivor command node 45160 so as to reflect an operative stateof the broadcasting ID node.

At step 4710, method 4700 continues with the primary command nodeconducting a primary container monitoring operation 4715 while theprimary command node is in a normal operating state (e.g., while primarycommand node 24160 is operating normally, has not entered a state ofceased communications, is responsively communicative with other nodes,such as the designated survivor command node 45150, and the like). Theprimary container monitoring operation 4710 is essentially a series ofsub steps 4715 a-4715 d performed by the primary command node (e.g.,exemplary primary command node 24160) while the primary command noderemains in the normal operating state. However, should the operatingstate of the primary command node change to become inoperative orincommunicative, the primary command node is then no longer able toperform the primary container monitoring operation 4715 and that taskwill shift (as explained above) to the designated survivor command nodeas part of step 4725.

In more detail, after step 4710, method 4700 has the primary commandnode proceeding to sub step 4715 a where the primary command nodemonitors the signal activity from each in the group of the wireless IDnodes. For example, such monitoring of the signal activity may involvedetecting sensor data broadcast from each in the group of the wirelessID nodes (when the ID nodes deployed as used in method 4700 aresensor-based wireless ID nodes, such as ID nodes 1-8 as describedabove). In a further embodiment of method 4700 as part of sub step 4715a when monitoring the signal activity involves detecting sensor databroadcast from each in the group of the wireless ID nodes, the step ofdetecting the sensor data broadcasted from each in the group of thewireless ID nodes may be implemented with the primary command nodedetecting the sensor data broadcasted by each in the group of thewireless ID nodes according to a broadcast profile maintained by each ofthe group of the wireless ID nodes. The broadcast profile (e.g., part ofexemplary profile data 330) defines a first messaging rate used toregulate how often the generated sensor data is broadcast, where thefirst messaging rate is higher than a default messaging rate. As such,the primary command node may then instruct each of the group of thewireless ID nodes to broadcast future generated sensor data at a secondmessaging rate that exceeds the first messaging rate after the primarycommand node transmits the layered alert notification to the externaltransceiver associated with the transit vehicle as part of sub step 4715d. Such instructions from the primary command node may instruct each ofthe group of the wireless ID nodes to change from the default messagingrate to the first messaging rate (e.g., a messaging rate for the IDnodes that has an initial value correlated to an environmental riskassociated with material maintained within the shipping container).

At sub step 4715 b, method 4700 continues with the primary command nodedetermining if it can responsively identify the environmental anomalybased upon the monitored signal activity from the ID nodes. If so, substep 4715 b proceeds to sub step 4715 c. Otherwise, sub step 4715 breturns back to monitoring signal activity from the wireless ID nodes insub step 4715 a. In more detail as part of sub step 4715 b and when, theprimary command node may responsively identify the environmental anomalyfor the shipping container when the detected sensor data does notinclude the sensor data from at least a threshold number of the wirelessID nodes, or when the detected sensor data indicates an environmentalcondition that exceeds an environmental threshold. In a furtherembodiment, the primary command node may responsively identify theenvironmental anomaly for the shipping container when the detectedsensor data does not include the sensor data from at least a thresholdnumber of the wireless ID nodes, and when the detected sensor dataindicates an environmental condition that exceeds an environmentalthreshold. The environmental condition and the environmental thresholdin such embodiments may be related to detected temperature, detectedpressure, detected radiation, or conditions and thresholds related to adetected chemical presence (such as the detected chemical presence isindicative of an explosive within the shipping container or the detectedchemical presence is indicative of a fire within the shippingcontainer).

At sub step 4715 c, method 4700 continues with the primary command nodegenerating a layered alert notification related to the environmentalanomaly for the shipping container in response to identifying theenvironmental anomaly for the shipping container in sub step 4715 b.Such a layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority. In more detail, the identified targetedmediation recipient may be identified as a triggered fire suppressionapparatus (e.g., exemplary fire suppression system 25010) on the transitvehicle that supplies a fire suppression agent into the shippingcontainer as the mediation response, or personnel (e.g., an operator orlogistics crew) related to operations of the transit vehicle that areprompted by the external transceiver as the mediation response. Thetargeted mediation action identified by the primary command node in thelayered alert notification may also be identified based upon an extentof an observed drop in the monitored signal activity from the ID nodesand what is loaded within the shipping container as indicated byshipping information maintained on the primary command node.Additionally, the mediation response priority established by the primarycommand node in the layered alert notification may be established basedupon an extent of an observed drop in the monitored signal activity fromthe wireless ID nodes, where the extent of the observed drop reflects apriority level for the mediation response priority that indicates one ofdifferent permissive status conditions for further travel by the transitvehicle.

At step 4715 d, method 4700 then has the primary command nodetransmitting the layered alert notification to an external transceiverdisposed separate from the shipping container to initiate a mediationresponse related to the targeted mediation action.

Thus, the sub steps 4715 a-4715 d essentially make up the processinvolved with the primary container monitoring operation 4715 performedwhile the primary command node is operative and communicative (e.g., ina normal state of operation). In more detail, the primary command nodeperforming sub steps 4715 a-4715 d may be implemented as a containernode mounted to the shipping container and operative to directlycommunicate with each in the group of the wireless ID nodes disposedinternal to the shipping container and to directly communicate with theexternal transceiver (e.g., external transceiver 24150 or thetransceiver part of fire suppression system 25010) associated with thetransit vehicle

However, step 4720 of method 4700 determines if the primary command nodehas been rendered inoperative (i.e., the primary command node is nolonger operative and able to perform the primary container monitoringoperation 4715). In more detail, the designated survivor command nodedetermines if the primary command node is no longer operative (e.g.,primary command node 24160 is not responsive to communications sent bydesignated survivor command node 45160 to primary command node 24160;primary command node is no longer sending out status messagesanticipated to be broadcast and received by the designated survivorcommand node 45160) as part of step 4720. As such and if step 4720determines the primary command node is still operative, step 4720proceeds back to step 4710. But if step 4720 determines the primarycommand is inoperative, step 4720 proceeds to step 4725 where thedesignated survivor command node is activated to step into the role ofthe primary command node and begin performing a backup containermonitoring operation (i.e., the same container monitoring operation 4715involving sub steps 4715(a)-(d) of the primary container monitoringoperation but now performed by the designated survivor command node inplace of the inoperative primary command node). Stated another way inmore detail, step 4725 may involve activating the backup containermonitoring operation with the designated survivor command nodeperforming sub steps (a)-(d) of the primary container monitoringoperation 4715 by a container node mounted to the shipping containeroperating as the designated survivor command node. As such, thedesignated survivor command node may then directly communicate with eachin the group of the wireless ID nodes disposed internal to the shippingcontainer as part of performing the primary container monitoringoperation 4715 and directly communicate with the external transceiver(e.g., external transceiver 24150 or the transceiver within firesuppression system 25010) associated with the transit vehicle

A further embodiment of method 4700 may use one of multiple differentprioritized survivor command nodes as the designated survivor commandnode involved in steps 4720 and 4725. For example, the step ofactivating the backup container monitoring operations in step 4725 bythe designated survivor command node when the primary command nodebecomes inoperative may further involve identifying one of multipleprioritized survivor command nodes associated with the primary commandnode to be the designated survivor command node based upon a priorityrank related each of the prioritized survivor command nodes (e.g., apriority rank related to how far away the particular prioritizedsurvivor command node is from the primary command node as disposedwithin the shipping container as the prioritized survivor command nodesare typically disposed at different physical locations within thecontainer, such as on opposing sides of the shipping container). Assuch, the one of the prioritized survivor command nodes identified to bethe designated survivor command node when the primary command nodebecomes inoperative may be the highest priority one of the prioritizedsurvivor command nodes that remains operative when the primary commandnode becomes inoperative. In a further example, the one of theprioritized survivor command nodes may be identified to be thedesignated survivor command node from the others of the prioritizedsurvivor command nodes when higher priority ranked ones of theprioritized survivor command nodes are unable to communicate with theprimary command node (e.g., the higher priority ranked ones are nolonger operative as well and, thus, an operative but next lower priorityranked one of the prioritized survivor command nodes may be used as thatdesignated survivor command node).

Another further embodiment of method 4700 may have step 4725 activatingthe backup container monitoring operation by activating the backupcontainer monitoring operation by the designated survivor command nodewhen the designated survivor command node is unable to communicate withthe primary command node within a threshold reporting interval. Inanother example, the step of activating the backup container monitoringoperation may involve preemptively activating the backup containermonitoring operation by the designated survivor command node when themonitored signal activity from each in the group of the wireless IDnodes indicates less than a threshold number of the wireless ID nodesare broadcasting.

Transitioned Monitoring Management for Environmental Anomaly

While the embodiments described above leverage another backup type ofcommand node within the shipping container, there are furtherembodiments that may transfer or transition the primary monitoringoperation related to monitoring wireless ID node signal activity withinthe shipping container from a command node mounted to the shippingcontainer to an external master node that can at least temporarily takeover the primary monitoring operation. For example, if a shippingcontainer is at a particular known or designated location (e.g., alocation within the transit vehicle, at a particular storage facility,and the like), a master node disposed separately and outside of theshipping container at that location may associate with the shippingcontainer's command node and take some of the processing burden off theshipping container's command node. In particular, for example, arrivingat that location can have the primary task of monitoring ID nodes for anenvironmental anomaly shifting from the container's command node to theexternal master node (passively monitoring the container's ID nodes),which may free up the command node for other management responsibilitiesor help save battery life on the command node itself. When leaving thatknown location, the responsibility may transition back from the externalmaster node to the container's command node. Some embodiments may havethe shipping container's command node initiating such a transition ofthe primary monitoring operation for detecting the environmental anomalywith an instruction to the external master node. Other embodiments mayhave the external master node proactively being the device thatinitiates the transition of primary monitoring operations from theshipping container's command node. Still further embodiments may havethe shipping container's command node initiating such a transition ofprimary monitoring operations when detecting it is close enough to theexternal master node and when the command node senses its own batterylevel is below a threshold where the transition of such monitoringoperations helps the command node preserve battery power and extend itsbattery life.

FIGS. 48A-48C are diagrams of an exemplary dynamic monitoring system foridentifying and responding to an environmental anomaly related to ashipping container using wireless ID nodes, a command node as a primarymonitor and external master node that is operative to temporarilyoperate as the primary monitor for the environmental anomaly inaccordance with an embodiment of the invention. Referring now to FIG.48A, an exemplary system 48000 a is shown similar to what is describedabove with reference to, for example, FIGS. 37A-37B, where a transitvehicle 24200 is shown with transit vehicle storage 24205. The transitvehicle 24200 is shown equipped with external transceiver 24150 (aspreviously described), which may communicate with remote control centerserver 24100 via network 24105 as well as communicate directly with eachof command node 24160 and wireless transceiver equipped fire suppressionsystem 25010. Within storage 24205, exemplary shipping container 24300 ais disposed such that fire suppression system 25010 may be activated(e.g., by external transceiver 24150 or by command node 24160) to supplya fire suppression agent into shipping container 24300 a (e.g., asexplained with reference to FIGS. 32A-32C).

In more detail and as illustrated in FIG. 48A, the system's shippingcontainer 24300 a is deployed to include exemplary command node 24160,which may communicate with external transceiver 24150 as well as withfire suppression system 25010. Command node 24160 is further operativeto communicate with various ID nodes disposed within or as part ofcontainer 24300 a. For example, as shown in FIG. 48A, command node 24160is operative to communicate with exemplary ID nodes 24120 a-24120 g(e.g., ID nodes 1-7) disposed within container 24300 a. Exemplary IDnodes 24120 a-24120 c (i.e., ID Nodes 1-3) are illustrated as beingrespectively associated with packages 24400 a-24400 c, while ID nodes24120 d-24120 g (i.e., ID Nodes 4-7) are disposed within shippingcontainer 24300 a without being associated with a package. As such, IDnodes 24120 d-24120 g (i.e., ID Nodes 4-7) may be part of the shippingcontainer or attached to the shipping container or may be simply an IDnode disposed within the shipping container without being fixed to theshipping container and without being associated with, attached to, ordisposed within a package in the shipping container.

Exemplary system 48000 a illustrated in FIG. 48A shows an additionalexternal master node, exemplary vehicle master node 48110 a, that may beused to temporarily operate as the primary monitor for an environmentalanomaly. This additional external master node may be implemented as atype of master node described relative to FIG. 4 and exemplary masternode 110 a. The external master node, as part of the embodimentsdescribed relative to FIGS. 48A-49B, is a master node that is disposedseparately from the shipping container 24300 a and operative totemporarily perform as the primary monitor of signal activity from IDnodes 1-7 under particular conditions where that primary monitoringoperation has been transitioned off the shipping container's own commandnode 24160 as described in more detail below. For example, as part ofsystem 48000 a, vehicle master node 48110 a is disposed separate fromthe shipping container 24300 a and is mounted as part of the transitvehicle 24200 (e.g., disposed in a known location within the transitvehicle 24200). As such, vehicle master node 48110 a may have a knownrelative location as disposed on transit vehicle 24200 and relative tothe movable location of the command node 24160 (i.e., the location ofcommand node 24160 as mounted to container 24300 a as the container24300 a moves relative to the transit vehicle 24200 and within thetransit vehicle storage 24205).

While only one vehicle master node 48110 a is illustrated in FIG. 48A,embodiments of system 48000 a may deploy more than one vehicle masternode 48110 a on transit vehicle 24200. Further, while the descriptionherein describes the particular interactions between vehicle master node48110 a and command node 24160 within shipping container 24300 a, thoseskilled in the art will appreciate that vehicle master node 48110 a mayconcurrently interact with and take over primary monitoring operationsfrom multiple different command nodes deployed on different shippingcontainers on transit vehicle 24200 and that similar concurrentinteracts may take place with other such command nodes on thosedifferent shipping containers. As such, the vehicle master node 48110 ain system 48000 a provides a robust wireless node network element thatcan help manage and offload monitoring operations involving thedetection of environmental anomalies with one or more shippingcontainers on transit vehicle 24200.

In another example, as shown in FIG. 48B, exemplary system 48000 bdeploys an external master node as a mobile master node 48110 b.Referring now to FIG. 48B, mobile master node 48110 b is disposedseparately from shipping container 24300 a, but may move relative to thecommand node 24160 of container 24300 a. In this situation, the distancebetween the command node 24160 of container 24300 a and mobile masternode 48110 b may change based upon movement of the container 24300 a,movement of the mobile master node 48110 b, or the combined movement ofboth the container 24300 a and mobile master node 48110 b. While theembodiment of system 48000 b is shown in the context of what is ontransit vehicle 24200, an embodiment of system 48000 b may be deployedoutside of a transit vehicle environment where the mobile master node48110 b and shipping container 24300 a may be operating more generallyto monitor for an environmental anomaly and transition such a primarymonitoring operation from the container's command node 24160 to themobile master node 48110 b.

In another example, as shown in FIG. 48C, exemplary system 48000 cdeploys an external master node as a facility master node 48110 c.Referring now to FIG. 48C, facility master node 48110 b is disposedseparately from shipping container 24300 a, and may be located at astorage facility used to temporarily house transit vehicle 24200. Thus,exemplary facility master node 48110 c is disposed external to shippingcontainer 24300 a and outside of transit vehicle 24200, but is stillclose enough and operative to communicate with ID nodes 1-7 withincontainer 24300 a so that facility master node 48110 c may temporarilytake over the functions of the primary monitor operations typicallyperformed by command node 24160 of container 24300 a.

FIGS. 49A-49B are diagrams illustrating examples where primary monitoroperations are transitioned within an exemplary dynamic monitoringsystem for identifying and responding to an environmental anomalyrelated to a shipping container. Referring now to FIG. 49A illustratingexemplary system 49000 (similar to that shown in FIG. 48A), system 49000uses wireless ID nodes 1-7, command node 24160 as the current primarymonitor for an environmental anomaly, and external vehicle master node48110 a that is operative to temporarily operate as the primary monitorfor the environmental anomaly in place of command node 24160 inaccordance with an embodiment of the invention. In more detail and asshown in FIG. 49A, exemplary command node 24160 is configured to operateas the primary monitor for an environmental anomaly in that command node24160 is shown at least wirelessly monitoring signal activity beingbroadcast from ID nodes 1-7 disposed within shipping container 24300 a.Such signal activity may, for example, be advertising signals broadcastfrom ID nodes 1-7. Such advertising signals may, in some instances,include sensor data generated by respective ones of ID nodes 1-7.

As part of exemplary system 49000, command node 24160 may determine itis located within a threshold distance from the known location of theexternal vehicle master node (e.g., via node locating techniquesdescribed above, via signaling with or from server 24100, via signalingwith or from vehicle master node 48110 a). As such, command node 24160may dynamically instruct the external vehicle master node 48110 a totemporarily operate as the primary monitor for the environmental anomalyrelated to shipping container 24300 a. In more detail, such a thresholddistance within which the command node 24160 should be from vehiclemaster node 48110 a may be a distance predetermined so that exemplaryvehicle master node 48110 a may be ensured to reliable receivecommunications from ID nodes 1-7 under normal conditions (e.g.,broadcasted signals from ID nodes 1-7, which may include sensor datafrom ID nodes 1-7, when no environmental anomaly is present). As aresult, vehicle master node 48110 a then temporarily begins to operateas the primary monitor for any environmental anomaly within shippingcontainer 24300 a as shown in FIG. 49B where vehicle master node 48110 ais shown at least wirelessly monitoring signal activity being broadcastfrom ID nodes 1-7 disposed within shipping container 24300 a.

In light of such exemplary systems and their components as described ineach of FIGS. 48A-49B, further more detailed embodiments of dynamicallytransitioning systems that monitor a shipping container for anenvironmental anomaly related to the shipping container are describedbelow. For example, one embodiment of such a dynamically transitioningsystem may generally include a group of wireless ID nodes (e.g., IDnodes 1-7 as shown in FIG. 48A) disposed within a shipping container(e.g., exemplary container 24300 a being transported by transit vehicle24200 including an external transceiver 24150), a command node (e.g.,exemplary command node 24160 as shown in FIG. 48A), and an externalmaster node (e.g., exemplary vehicle master node 48110 a as shown inFIG. 48A).

The group of wireless ID nodes disposed within the shipping containerhave some of the ID nodes (which may or may be implemented assensor-based ID nodes) associated with one or more objects beingtransported in the shipping container (e.g., ID nodes 1-3 beingassociated with packages 1-3 as shown in FIG. 48A). As part of thisembodiment, the system's command node is mounted to the shippingcontainer and operative to directly communicate with the ID nodesdisposed internal to the shipping container. As such, the command nodeis configured (e.g., via program code that is part of command nodecontrol and management code 26425 and with wireless communicationinterfaces 26480, 26485) to operate as a primary monitor for theenvironmental anomaly.

The system's command node performs the primary monitor operations by,for example, being operative to (a) wirelessly monitor signal activitybeing broadcast from the ID nodes; (b) responsively identify theenvironmental anomaly based upon the monitored signal activity from theID nodes (e.g., which ID nodes are broadcasting, what sensor data isbeing broadcasted compared to particular thresholds, and the like); (c)generate the layered alert notification related to the environmentalanomaly for the shipping container in response to identifying theenvironmental anomaly for the shipping container (where the layeredalert notification identifies a targeted mediation recipient, identifiesa targeted mediation action, and establishes a mediation responsepriority); and (d) transmit the layered alert notification to theexternal transceiver to initiate a mediation response related to thetargeted mediation action. Thus, as deployed within the shippingcontainer, the system's command node is programmatically configured toperform and conduct at least operations (a)-(d) as the primary monitorfor the shipping container's environmental anomaly.

The system's external master node in this embodiment (even when it isselected from one of many external support master nodes disposedthroughout the transit vehicle) is disposed at a known location withinthe transit vehicle, such as a particular location within a storage areaof the transit vehicle (e.g., disposed on the ceiling or within thefloor within the middle of storage 24205 of transit vehicle 24200). Forexample, the external master node may be implemented by exemplaryvehicle master node disposed at a particular location on transit vehicle24200. The system's external master node may be a particular one of manyvehicle master nodes deployed along the transit vehicle storage 24205 soas to provide differently located external master nodes that maycommunicate with the command node 24160 of container 24300 a while alsobe able to communicate with the ID nodes 1-7 within container 24300 agiven the relative location of the particular external master node tothe command node 24160 of container 24300 a. In more detail, such anexternal master node may be implemented as a dual wireless transceiverbased processing device mounted on the transit vehicle (e.g., a masternode 110 a having two wireless transceivers 480, 485), where one of thedual wireless transceivers (e.g., interface 480) is operative towirelessly monitor the signal activity being broadcast from the ID nodesand a second of the dual wireless transceivers (e.g., interface 485) isoperative to wirelessly transmit the layered alert notification to theexternal transceiver to initiate the mediation response related to thetargeted mediation action.

Within this system embodiment, the system's command node is furtherconfigured to dynamically instruct the external master node totemporarily operate as the primary monitor for the environmental anomalywhen the command node determines a current location of the command nodeto be within a threshold distance from the known location of theexternal master node. For example, as shown in FIG. 49A, command node24160 is initially operating as the primary monitor for theenvironmental anomaly (e.g., conducting at least operations (a)-(d) asthe primary monitor for the shipping container's environmental anomalyas described above). However, container 24300 a may be located to bewithin a threshold distance of vehicle master node 48110 a (or relocatedto come within the threshold distance of vehicle master node 48110 a).Under such conditions, the command node 24160 in container 24300 a mayinstruct vehicle master node 48110 a to temporarily operate as theprimary monitor for the environmental anomaly as it related to shippingcontainer 24300 a as shown in FIG. 49B (e.g., conducting at leastoperations (a)-(d) as the primary monitor for the environmental anomalyas described above for shipping container 24300 a).

In more detail, the command node may dynamically instruct the externalmaster node to temporarily operate as the primary monitor for theenvironmental anomaly by being further operative to detect anadvertising signal broadcast from the external master node as thecommand node approaches the known location of the external master node(e.g., as command node 24160 within shipping container 24300 a movestowards the location of vehicle master node 48110 a as located withinthe transit vehicle 24200). As the command node approaches the externalmaster node, the command node may then dynamically instruct the externalmaster node to temporarily operate as the primary monitor for theenvironmental anomaly involving functions (a)-(d) as described above inresponse to detecting the advertising signal broadcast from the externalmaster node. Thus, the command node may “sense” the external master nodefrom the detected advertising signal emanating from the external masternode (e.g., an advertising signal that may not have been prompted by thecommand node but, instead, is more passively detected so as to indicatebeing within the threshold distance so as to enable the external masternode to be able to take over the primary monitor functions from thecommand node, which involves monitoring signal activity of ID nodeswithin the command node's shipping container).

In another example, a logical association may be established between thecommand node and external master node as part of transitioning primarymonitor duties by the system's command node. Such an association may beauthorized by a separate server (such as server 24100) and may betracked by such a server to manage the current logical associationsbetween particular node elements used as part of this dynamic systemthat monitors for an environmental anomaly. For example, the system'scommand node may dynamically instruct the external master node totemporarily operate as the primary monitor for the environmental anomalyby being further operative to first detect an advertising signalbroadcast from the external master node as the command node approachesthe known location of the external master node; then generateassociation data on the command node (e.g., association data 440) toassociate the command node with the external master node and reflect anauthorized pairing of the command node and the external master node; anddynamically instruct the external master node to temporarily operate asthe primary monitor for the environmental anomaly involving functions(a)-(d) as the command node transitions to a non-monitoring mode inresponse to associating the command node with the external master node.Such a non-monitoring mode of the command node allows the externalmaster node to be temporarily responsible for performing at least theprimary monitor functions (a)-(d) noted above, while allowing thecommand node to offload the processing burden and power usage that comeswith such primary monitor operations (e.g., allows command node 24160 toenter a low power mode to save on battery power, allows command node24160 to focus on other management duties with respect to ID nodesdisposed within shipping container 24300 a without having to incur theprocessing overhead and power drain from its onboard battery systemrelated to the primary monitor duties as set forth at least by functions(a)-(d) above).

In even more detail, the system's command node may dynamically instructthe external master node to temporarily operate as the primary monitorfor the environmental anomaly by being further operative to first detectthe current location of the command node (e.g., via self-location usingGPS circuitry on the command node, via location data 455 maintained inmemory of the command node, via location data received requested andreceived by the command node) and determine if the command node'scurrent location is within the threshold distance from the externalmaster node. When the current location of the command node is within thethreshold distance from the external master node, the command node maythen generate association data on the command node to associate thecommand node with the external master node. Such generated associationdata reflects a logical and authorized pairing of the command node andthe external master node. The command node may then dynamically instructthe external master node to temporarily operate as the primary monitorfor the environmental anomaly involving functions (a)-(d) as the commandnode transitions to a non-monitoring mode in response to associating thecommand node with the external master node, where the command node'snon-monitoring mode allows the external master node to be temporarilyresponsible for performing functions (a)-(d).

In a further example, the command node may dynamically instruct theexternal master node to temporarily operate as the primary monitor forthe environmental anomaly by being further operative to first broadcasta transition command to the external master node as the command nodeapproaches the known location of the external master node, and thenreceive an acknowledgement message from the external master node inresponse to the transition comment. Such an acknowledgement message isindicative of the external master node receiving the transition commandfrom the command node. The command node may then generate associationdata (e.g., generate and store data maintained as part of associationdata 440 in memory of the command node) to associate the command nodewith the external master node and reflect an authorized pairing of thecommand node and the external master node. Thereafter, the command nodemay dynamically instruct the external master node to temporarily operateas the primary monitor for the environmental anomaly involving functions(a)-(d) as the command node transitions to a non-monitoring mode inresponse to associating the command node with the external master node,where the non-monitoring mode of the command node allows the externalmaster node to be temporarily responsible for performing functions(a)-(d).

In another example, the transition may be based upon a transitioncommand sent by the command node without requiring the particulars ofestablishing a formal and logical association between the command nodeand the external master node. For example, the command node maydynamically instruct the external master node to temporarily operate asthe primary monitor for the environmental anomaly by being furtheroperative to broadcast a transition command from the command node to theexternal master node as the command node approaches the known locationof the external master node, and then receive an acknowledgement messageby the command node from the external master node in response to thetransition comment. Such an acknowledgement message is indicative of theexternal master node receiving the transition command from the commandnode. Accordingly, in response to receiving the acknowledgement message,the command node may then dynamically instruct the external master nodeto temporarily operate as the primary monitor for the environmentalanomaly involving functions (a)-(d) as the command node transitions to anon-monitoring mode in response to associating the command node with theexternal master node, where the non-monitoring mode of the command nodeallows the external master node to be temporarily responsible forperforming functions (a)-(d).

In a further embodiment, the system's command node may later resumeprimary monitor operations. For example, the system's command node(e.g., command node 24160) may subsequently instruct the external masternode to transition out of its role as the primary monitor for theenvironmental anomaly in order allow the command node to resumeoperating as the primary monitor for the environmental anomalyresponsible for performing functions (a)-(d). Such a transition back tothe command node may happen when the command node (e.g., the shippingcontainer 24300 a with command node 24160) moves outside the thresholddistance from the external master node (e.g., when the command nodedetermines a subsequent location of the command node is no longer withinthe threshold distance from the known location of the external masternode).

In an example where the command node and the external master nodeassociated as part of transitioning the primary monitor operationtemporarily to the external master node, the command node may determinethat its subsequent location is no longer within the threshold distancefrom the known location of the external master node. As a result, thecommand node may subsequently instruct the external master node totransition from the primary monitor for the environmental anomaly inorder allow the command node to resume operating as the primary monitorfor the environmental anomaly responsible for performing functions(a)-(d); and alter the association data on the command node to reflect adisassociation of the command node and the external master node inresponse to when the command node resumes operating as the primarymonitor for the environmental anomaly.

As mentioned above, embodiments of a dynamic monitoring system may havethe external master node being one of multiple different external masternodes disposed at different respectively known locations within thetransit vehicle. In other words, the group of different external masternodes may be referenced as external support master nodes as disposed atlocations within the transit vehicle, and the system's external masternode may be one of these different externally disposed master nodes(e.g., the vehicle master node 48110 a). As such, the command node maybe configured to dynamically instruct one of the external support masternodes (e.g., vehicle master node 48110 a if other vehicle master nodesare deployed at different locations on transit vehicle 24200) totemporarily operate as the primary monitor for the environmental anomalywhen the command node determines the current location of the commandnode to be within the threshold distance from the respectively knownlocation of the one of the external support master nodes.

In further embodiments where multiple external master nodes may bedisposed on the transit vehicle, the command node may transition theprimary monitor operations to different external master nodes. Forexample, the command node may be further configured to dynamicallyinstruct a second of the external support master nodes to temporarilyoperate as the primary monitor for the environmental anomaly from theone of the external support master nodes when the command nodedetermines a subsequent location of the command node to be within thethreshold distance from the respectively known location of the second ofthe external support master nodes.

In like fashion, another example may have the primary monitor dutiesgoing to one external master node, then back to the command node, andthen subsequently to another external master node. For example and inmore detail, the command node may subsequently instruct the one of theexternal support master nodes to transition from the primary monitor forthe environmental anomaly in order allow the command node to resumeoperating as the primary monitor for the environmental anomalyresponsible for performing functions (a)-(d); and then dynamicallyinstruct a second of the external support master nodes to temporarilyoperate as the primary monitor for the environmental anomaly when thecommand node determines a subsequent location of the command node to bewithin the threshold distance from the respectively known location ofthe second of the external support master nodes.

As mentioned above, an effect of transitioning the primary monitoroperation functions (a)-(d) from the command node to the external mastermay include power savings on the command node. As such, an example mayhave the command node being operative to shift to a reduced poweroperating mode after dynamically instructing the external master node totemporarily operate as the primary monitor for the environmentalanomaly. The reduced power operating mode, in general, is for thecommand node to conduct normal operations other than the primary monitoroperation functions (a)-(d), but may further have the command node entera sleep or hibernate mode where the command node temporarily goes into aminimal power draw state or turns off particular circuitry within thecommand node to save power but where the command may re-activate suchcircuitry to “wake” from such a reduced power operating mode. In moredetail, the command node may be operative to shift to such a reducedpower operating mode after receiving an acknowledgement message from theexternal master node, where the acknowledgement message indicates thatthe external master node is temporarily operating as the primary monitorfor the environmental anomaly. This may provide some overlappingmonitoring functionality by the command node and the external masternode before the external master node issues the acknowledgement messageand the command node is assured the transition of primary monitoringduties have been at least temporarily effective.

In still a further example, the command node may be operative to shiftto such a reduced power operating mode after dynamically instructing theexternal master node to temporarily operate as the primary monitor forthe environmental anomaly when (a) the command node determines a currentlocation of the command node to be within a threshold distance from theknown location of the external master node and (b) the command nodedetermines a battery status level for the command node is less than abattery level threshold. As such, the command node may detect thebattery status level and compare it to a battery level threshold in someinstances before or as a condition for transitioning the primary monitoroperation functions (a)-(d) to the external master node.

In another embodiment of a dynamic monitoring system for identifying andresponding to an environmental anomaly related to a shipping container,the system's external master node may not be specifically located at aparticular or known location (e.g., it may not be located apredetermined location in the transit vehicle's storage area). Instead,the system's external master node may, for example, be a mobile masternode (e.g., mobile master node 48110 b) that may be untethered to aspecific or fixed location. Such an embodiment of a dynamicallytransitioning system may generally include a group of wireless ID nodes(e.g., ID nodes 1-7 as shown in FIG. 48B) disposed within a shippingcontainer (e.g., exemplary container 24300 a being transported bytransit vehicle 24200 including an external transceiver 24150), acommand node (e.g., exemplary command node 24160 as shown in FIG. 48B),and an external master node (e.g., exemplary mobile master node 48110 bas shown in FIG. 48B).

The group of wireless ID nodes in this embodiment are disposed withinthe shipping container where at least a portion of the ID nodes (whichmay or may be implemented as sensor-based ID nodes) are respectivelyassociated with one or more objects being transported in the shippingcontainer (e.g., ID nodes 1-3 being associated with packages 1-3 asshown in FIG. 48A). The system's command node in this embodiment ismounted to the shipping container and operative to directly communicatewith the ID nodes disposed internal to the shipping container. As such,the command node is configured (e.g., via program code that is part ofcommand node control and management code 26425 and with wirelesscommunication interfaces 26480, 26485) to operate as a primary monitorfor the environmental anomaly.

Similar the prior embodiment, this embodiment's command node performsthe primary monitor operations by, for example, being operative to (a)wirelessly monitor signal activity being broadcast from the ID nodes;(b) responsively identify the environmental anomaly based upon themonitored signal activity from the ID nodes (e.g., which ID nodes arebroadcasting, what sensor data is being broadcasted compared toparticular thresholds, and the like); (c) generate the layered alertnotification related to the environmental anomaly for the shippingcontainer in response to identifying the environmental anomaly for theshipping container (where the layered alert notification identifies atargeted mediation recipient, identifies a targeted mediation action,and establishes a mediation response priority); and (d) initiate amediation response related to the targeted mediation action bybroadcasting the layered alert notification. Thus, as deployed withinthe shipping container, the system embodiment's command node isprogrammatically configured to perform and conduct at least operations(a)-(d) as the primary monitor for the shipping container'senvironmental anomaly.

The system's external master node in this further embodiment is disposedseparately from the command node and, as a type of master node, isconfigured to communicate with the command node over its wirelesscommunication interfaces.

In more detail, such an external master node may be implemented as adual wireless transceiver based processing device mounted on the transitvehicle (e.g., a master node 110 a having two wireless transceivers 480,485), where one of the dual wireless transceivers (e.g., interface 480)is operative to wirelessly monitor the signal activity being broadcastfrom the ID nodes and a second of the dual wireless transceivers (e.g.,interface 485) is operative to wirelessly transmit the layered alertnotification to the external transceiver to initiate the mediationresponse related to the targeted mediation action.

Within this further system embodiment, the system's command node isconfigured to dynamically instruct the external master node totemporarily operate as the primary monitor for the environmental anomalywhen the command node determines a current location of the command nodeto be within a threshold distance from a current location of theexternal master node. For example, command node 24160 may determine itis located within a threshold distance from a current location of theexternally disposed mobile master node 48110 b (e.g., via self-locationusing GPS circuitry on the command node 24160, via location data 455maintained in memory of the command node 24160, via location datareceived requested and received by the command node 24160, via nodelocating techniques described above to determine the location of themobile master node 48110 b, via signaling with or from server 24100, viasignaling with or from mobile master node 48110 b requesting suchlocation information).

In more detail, command node in this embodiment may dynamically instructthe external master node to temporarily operate as the primary monitorfor the environmental anomaly by being further operative to detect anadvertising signal broadcast from the external master node as thedistance between the command node and the external master node decreases(i.e., the command node and external master node close in relative toeach other), and dynamically instruct the external master node totemporarily operate as the primary monitor for the environmental anomalyinvolving functions (a)-(d) in response to detecting the advertisingsignal broadcast from the external master node.

The system embodiment may specifically have the external master nodebeing a mobile external master node (e.g., mobile master node 48110 b)movably disposed external to the command node. As such, the command nodemay dynamically instruct the mobile external master node to temporarilyoperate as the primary monitor for the environmental anomaly by beingfurther operative to detect an advertising signal broadcast from themobile external master node as a distance between the command node andthe mobile external master node decreases as a result of the mobileexternal master node moving closer to the command node, and dynamicallyinstruct the mobile external master node to temporarily operate as theprimary monitor for the environmental anomaly involving functions(a)-(d) in response to detecting the advertising signal broadcast fromthe mobile external master node.

In another example, the system's command node may dynamically instructthe external master node to temporarily operate as the primary monitorfor the environmental anomaly using associations by being furtheroperative to detect an advertising signal broadcast from the externalmaster node as the command node approaches the location of the externalmaster node; generate association data on the command node to associatethe command node with the external master node and reflect an authorizedpairing of the command node and the external master node; anddynamically instruct the external master node to temporarily operate asthe primary monitor for the environmental anomaly involving functions(a)-(d) as the command node transitions to a non-monitoring mode inresponse to associating the command node with the external master node(where the command node's non-monitoring mode allows the external masternode to be temporarily responsible for performing functions (a)-(d) andwhere the command node no longer operates in a manner to performfunctions (a)-(d)).

In a more detailed another example involving association data, thesystem's command node may dynamically instruct the external master nodeto temporarily operate as the primary monitor for the environmentalanomaly by being further operative to detect the current location of thecommand node and the external master node; determine if the currentlocation of the command node is within the threshold distance from thecurrent location of the external master node; generate association dataon the command node to associate the command node with the externalmaster node when the current location of the command node is within thethreshold distance from the current location of the external masternode, the generated association data reflecting an authorized pairing ofthe command node and the external master node; and dynamically instructthe external master node to temporarily operate as the primary monitorfor the environmental anomaly involving functions (a)-(d) as the commandnode transitions to a non-monitoring mode in response to associating thecommand node with the external master node (where the non-monitoringmode of the command node allows the external master node to betemporarily responsible for performing functions (a)-(d) and where thecommand node no longer operates in a manner to perform functions(a)-(d)).

In yet another example, the command node may dynamically instruct theexternal master node to temporarily operate as the primary monitor forthe environmental anomaly based on a transition command by being furtheroperative to broadcast a transition command from the command node to theexternal master node as the command node approaches the external masternode, and receive an acknowledgement message by the command node fromthe external master node in response to the transition command (wheresuch an acknowledgement message indicates the external master nodereceived the transition command from the command node). The command nodemay then be further operative to generate association data on thecommand node to associate the command node with the external master nodeand reflect an authorized pairing of the command node and the externalmaster node, and dynamically instruct the external master node totemporarily operate as the primary monitor for the environmental anomalyinvolving functions (a)-(d) as the command node transitions to anon-monitoring mode in response to associating the command node with theexternal master node, the non-monitoring mode of the command nodeallowing the external master node to be temporarily responsible forperforming functions (a)-(d).

Another example may have the command node dynamically instructing theexternal master node to temporarily operate as the primary monitor forthe environmental anomaly by being further operative to broadcast atransition command from the command node to the external master node asthe command node approaches the external master node; receive anacknowledgement message by the command node from the external masternode in response to the transition command (where the acknowledgementmessage receipt of the transition command from the command node); andthen respond by dynamically instructing the external master node totemporarily operate as the primary monitor for the environmental anomalyinvolving functions (a)-(d) as the command node transitions to anon-monitoring mode in response to associating the command node with theexternal master node, the non-monitoring mode of the command nodeallowing the external master node to be temporarily responsible forperforming functions (a)-(d).

In a further embodiment, the above-described system may have the commandnode later resuming the primary monitor operation from the externalmaster node. For example and in more detail, the command node maysubsequently instruct the external master node to transition from theprimary monitor for the environmental anomaly in order allow the commandnode to resume operating as the primary monitor for the environmentalanomaly responsible for performing functions (a)-(d). Such a subsequentinstruction may be sent by the command node when the command nodedetermines a subsequent location of the command node is no longer withinthe threshold distance from the external master node. As such, thecommand node may send this subsequent instruction and may also, in someembodiments, alter the association data on the command node to reflect adisassociation of the command node and the external master node inresponse to when the command node resumes operating as the primarymonitor for the environmental anomaly.

A further embodiment of the above-described system embodiment mayfurther include an external transceiver disposed on a transit vehicletransporting the shipping container. As such, the command node may theninitiate the mediation response related to the targeted mediation actionby broadcasting the layered alert notification to the externaltransceiver disposed on a transit vehicle transporting the shippingcontainer. In more detail, such an external transceiver disposed on thetransit vehicle may be implemented as a display-based externaltransceiver (e.g., exemplary transceiver 24150 that may include adisplay 40015 as shown in FIG. 40) operative to receive the layeredalert notification and generate a prompt notification on the displaythat provides mediation instructions on the targeted mediation action.Such a prompt notification may include instructions for an operator ofthe transit vehicle to change course of the transit vehicle as themediation instructions, or instructions for a logistics crew on thetransit vehicle to inspect the shipping container as the mediationinstructions. Alternatively, such an external transceiver disposed onthe transit vehicle may be implemented as a wireless transceiverequipped fire suppression system (e.g., exemplary fire suppressionsystem 25010 having transceiver communication interface 32010 as shownin FIGS. 32A-32C) operative to receive the layered alert notificationand supply a fire suppression agent into the shipping container as thetargeted mediation action.

A further system embodiment may have the external master node initiatinga request to serve as the primary monitor. In more detail, such afurther embodiment may include the group of ID nodes and command node asdescribed above, and also include an external master node disposed at aknown location within the transit vehicle. The external master node isconfigured to communicate with the command node and, in particular, isfurther configured to (a) dynamically instruct the command node to stopoperating as the primary monitor for the environmental anomaly (i.e.,the primary monitor operating functions (a)-(d) described above) and (b)temporarily operate as the primary monitor for the environmental anomalywhen the external master node determines a current location of thecommand node to be within a threshold distance from the location of theexternal master node.

Further still, another system embodiment may rely upon a backend serverto initiate changing which of the command node or the external masternode is to be operating as the primary monitor for an environmentalanomaly related to a shipping container. For example, such a dynamicallytransitioning system for monitoring a shipping container for anenvironmental anomaly related to the shipping container includes a groupof wireless ID nodes disposed within the shipping container (e.g., IDnodes 1-7 as shown in FIG. 49A within shipping container 24300 a), acommand node mounted to the shipping container (e.g., command node24160), an external master node disposed separate from the shippingcontainer and on the transit vehicle (e.g., vehicle master node 48110 a,which is configured to communicate with the command node), and a backendremote server (e.g., server 24100) configured to communicate with thecommand node and with the external master node over a network (e.g.,network 24105).

In this additional system embodiment (similar to the other dynamicsystem embodiments described above), the command node is operative todirectly communicate with the ID nodes disposed internal to the shippingcontainer and is configured to operate as a primary monitor for theenvironmental anomaly by being operative to (a) wirelessly monitorsignal activity being broadcast from the ID nodes; (b) responsivelyidentify the environmental anomaly related to the shipping containerbased upon the monitored signal activity from the ID nodes; (c) generatethe layered alert notification related to the environmental anomalyrelated to the shipping container in response to identifying theenvironmental anomaly for the shipping container (where the layeredalert notification identifies a targeted mediation recipient, identifiesa targeted mediation action, and establishes a mediation responsepriority); and (d) transmit the layered alert notification to theexternal transceiver to initiate a mediation response related to thetargeted mediation action). The backend remote server is furtherconfigured, when the backend remote server determines a current locationof the command node to be within a threshold distance from a currentlocation of the external master node, to be operative to (i) instructthe command node to stop operating as the primary monitor for theenvironmental anomaly related to the shipping container, and (ii)instruct the external master node to temporarily operate as the primarymonitor for the environmental anomaly related to the shipping container.

The backend server's instructions may also be authenticated as part ofchanging responsibility for the primary monitor operation for anenvironmental anomaly related to the shipping container. For example,the command node may be further configured to transmit an authenticationrequest to the backend remote server. Such an authentication request isrelated to an instruction for the command node to stop operating as theprimary monitor for the environmental anomaly related to the shippingcontainer. The command node may then be further operative to ceaseoperating as the primary monitor for the environmental anomaly relatedto the shipping container when the command node receives anacknowledgement message from the backend remote server confirming theinstruction for the command node to stop operating as the primarymonitor for the environmental anomaly related to the shipping container.In like manner, the external master node may be further configured totransmit an authentication request to the backend remote server (wherethe authentication request is related to an instruction for the externalmaster node to begin temporarily operating as the primary monitor forthe environmental anomaly related to the shipping container) and begintemporarily operating as the primary monitor for the environmentalanomaly related to the shipping container when the external master nodereceives an acknowledgement message from the backend remote serverconfirming the instruction for the external master node to begintemporarily operating as the primary monitor for the environmentalanomaly related to the shipping container.

At a later point in time, the command node in this embodiment may resumeprimary monitor operations at the instruction of the backend server. Forexample, the backend remote server may instruct the external master nodeto stop temporarily operating as the primary monitor for theenvironmental anomaly related to the shipping container, and instructthe command node to resume operating as the primary monitor for theenvironmental anomaly related to the shipping container.

Additionally, the system's backend server may also transition theprimary monitor duties for the shipping container from one externalmaster node to another external master node. For example, the backendremote server may be further configured to be operative to instruct theexternal master node to stop temporarily operating as the primarymonitor for the environmental anomaly related to the shipping container,and instruct another external master node to begin temporarily operatingas the primary monitor for the environmental anomaly related to theshipping container. As such, the backend server may directly andactively manage which of the potential external master nodes disposednear a shipping container may be deployed to temporarily take over theprimary monitoring for an environmental anomaly related to the shippingcontainer, as well as moving such monitoring responsibilities betweendifferent external master nodes as needed (e.g., as the shippingcontainer moves between locations where different external master nodesare disposed).

Further still, the system's backend server may direct the transition ofthe primary monitoring operation responsibilities from one externalmaster node, back to the command node, and then to anther externalmaster node. For example, the backend remote server may be furtherconfigured to be operative to instruct the external master node to stoptemporarily operating as the primary monitor for the environmentalanomaly related to the shipping container; instruct the command node toresume operating as the primary monitor for the environmental anomalyrelated to the shipping container; instruct the command node to stopoperating as the primary monitor for the environmental anomaly relatedto the shipping container after having resumed operating as the primarymonitor; and then instruct another external master node to temporarilyoperate as the primary monitor for the environmental anomaly related tothe shipping container.

In still a further system embodiment, the system's command node may befurther configured to dynamically instruct the external master node (oranother shipping container's command node or a secondary command nodedeployed within the same shipping container) to temporarily operate asthe primary monitor for the environmental anomaly when the command nodedetermines a current location of the command node to be within athreshold distance from the known location of the external master node(or the other shipping container's command node or the second commandnode deployed within the same shipping container). For example, as shownin FIG. 49A, command node 24160 is initially operating as the primarymonitor for the environmental anomaly (e.g., conducting at leastoperations (a)-(d) as the primary monitor for the shipping container'senvironmental anomaly as described above). However, container 24300 amay be located to be within a threshold distance of vehicle master node48110 a (or relocated to come within the threshold distance of vehiclemaster node 48110 a or located to be within a communication distance toanother shipping container's command node or a secondary command nodedeployed within container 24300 a). Under such conditions, the commandnode 24160 in container 24300 a may instruct vehicle master node 48110 a(or the other shipping container's command node) to temporarily operateas the primary monitor for the environmental anomaly as it relates toshipping container 24300 a as shown in FIG. 49B (e.g., conducting atleast operations (a)-(d) as the primary monitor for the environmentalanomaly as described above for shipping container 24300 a). Further, inthis situation, command node 24160 in container 24300 a may dispensewith expending battery power and processing cycles to perform operations(a)-(d) and, instead, become an enhanced sensor-based ID node to bemonitored by vehicle master node 48110 a by using one or more sensors(e.g., 26465) on command node 24160 in container 24300 a and broadcastsensor data generated by command node 24160 to vehicle master node 48110a. As such, vehicle master node 48110 a may perform the (a) wirelesslymonitor signal activity being broadcast from the ID nodes (now includingsignal activity broadcast from command node 24160 as an additionalsensor-based ID node using the command node's own sensors); (b)responsively identify the environmental anomaly based upon the monitoredsignal activity from the ID nodes (e.g., which ID nodes are broadcastingincluding the command node operating as the enhanced sensor-based IDnode, what sensor data is being broadcasted (including the commandnode's sensor data) compared to particular thresholds, and the like). Inthis way, the command node's own sensors (which may have a broader arrayof sensors, more accurate sensors, and more sensing elements) may allowthis type of monitor responsibility shift to provide an even greaterlevel of sensing and better use of command node battery power andcompute cycles to more accurately detect potential environmentalanomalies. In this example, command node 24160 may also similarlytransition back to assuming operations (a)-(d) as well and similar tothat described above.

Integrated Fire Suppression System

As shown and described in embodiments above, an exemplary firesuppression system (such as exemplary onboard triggered fire suppressionsystem 25010) may be activated and deployed on a transit vehicle forinitiating a mediation action in response to a detected environmentalanomaly related to a shipping container being transported on the transitvehicle. As noted above, an embodiment of such an exemplary firesuppression system 25010 as shown in FIGS. 32A-32C may generally includeat least a fire suppression controller 32000, a transceiver 32010coupled to the controller, a pump 32015, a fire suppression agentreservoir chamber 32020 that holds a fire suppression agent, andactuators 32025 a-32025 b that responsively control an articulatingneedle 32030 a-32030 b as a type of dispenser coupled to the pump andthat may be extended to puncture a shipping container 24300 a on thetransit vehicle 24200. Further embodiments may implement such anexemplary fire suppression system with an integrated master node, whichmay allow the fire suppression system to take on the primary monitoringoperation involving monitoring signal activity from ID nodes and/orsensor data from various types of sensors associated with the firesuppression system. In more detail, such a further embodiment of thefire suppression system may deploy additional sensors for monitoring theinside and/or outside of the shipping container to further assessenvironmental conditions of the shipping container itself and/orconditions within the container. Thus, rather than having a command nodewithin the shipping container conduct the primary monitoring operationand coordinate separately with an onboard fire suppression system,embodiments may have the onboard fire suppression system take on theprimary monitoring responsibility for detecting an environmental anomalyas well as provide for advanced assessments involved in such detectingand improved mediation responses. Furthermore, similar to that describedabove, having the onboard fire suppression system take on the primarymonitoring responsibility for detecting an environmental anomaly may letthe command node within the shipping container assume the role of anenhanced ID node using the command node's wider array of more powerfuland/or sensitive sensors (given the availability of more power from thecommand node's battery or if the command node is powered via a lineconnection to the shipping container and to an external power source(e.g., a generator onboard the transit vehicle)).

FIGS. 50A-50C are a series of diagrams of another exemplary onboard firesuppression system having an integrated master node and be activated anddeployed on a transit vehicle for monitoring for an environmentalanomaly and initiating a mediation action in response to a detectedenvironmental anomaly related to a shipping container being transportedon the transit vehicle in accordance with an embodiment of theinvention. Referring now to FIG. 50A, exemplary system 50000 is shown ashaving similar components illustrated and described relative to FIG.32A, but includes a different embodiment of the fire suppression systemwhen compared to system 25010 shown in FIG. 32A. In particular,exemplary onboard fire suppression system 25010 a is illustrated inFIGS. 50A-50C with similar components as fire suppression system 25010from FIGS. 32A-32C, but exemplary fire suppression system 25010 aincludes fire suppression master node 50110 (e.g., a type of master node110 a as described above) in place of the transceiver 32010 and firesuppression controller 32000 of system 25010 shown in FIG. 32A. Ingeneral, fire suppression master node 50110 has functionality that isprogrammatically configured by virtue its master node management andcontrol code (e.g., code 425) as explained in more detail below. Similarto the fire suppression controller 32000 from fire suppression system25010, the exemplary fire suppression master node 50110 in firesuppression system 25010 a is also operative generate the pump controlinput for pump 32015 and cause the articulating delivery nozzle 32030 a,32030 b to deploy (via actuators 32025 a, 32025 b) and deliver the firesuppressant material to the shipping container.

Additionally, the fire suppression master node 50110 is programmaticallyconfigured to operate as a primary monitor for the environmental anomalyrelated to shipping container 24300 a in how it can interact with IDnodes 1-6 and respond accordingly. In more detail and as firesuppression master node 50110 executes its master node management andcontrol code, fire suppression master node 50110 becomesprogrammatically configured to be operative to (a) wirelessly monitorthe signals being broadcast from the ID nodes 1-6; (b) responsivelyidentify the environmental anomaly based upon the monitored signalsbroadcast from the ID nodes 1-6 (e.g., advertising signals, signalsincluding sensor data, and the like); (c) generate a layered alertnotification related to the environmental anomaly for the shippingcontainer in response to identifying the environmental anomaly for theshipping container (where the layered alert notification identifies atargeted mediation action and establishes a mediation responsepriority); and (d) initiate a mediation response by the fire suppressionsystem 25010 a related to the targeted mediation action and themediation response priority (such as dispensing the fire suppressionagent material into the shipping container 24300 a). As such, the firesuppression master node 50110 may take on the role of the shippingcontainer's command node in such embodiments.

As shown in FIG. 50B (similar to that shown in FIG. 32B), actuators maybe activated by the fire suppression master node 50110 so that aparticular actuator, such as actuator 32035 a, responsively articulates,moves, and/or extends its needle 32030 a (part of an exemplaryarticulating delivery nozzle) from a retracted position to an extendedactivated position (as shown in FIG. 50B). In this way, the extendedneedle 32030 a and its actuator 32025 a (collectively an example of anarticulating delivery nozzle) are forcibly deployed to rapidly create anopening in a shipping container (e.g., shipping container 24300 a shownin FIGS. 50A-50C) in response to a deployment control signal sent fromthe fire suppression master node 50110 to the respective actuator (e.g.,actuator 32025 a) as part of initiating a type of mediation action aspart of the above described primary monitoring operation (d). Once thedispensing articulated puncture (e.g., actuator 32025 a and its relatedneedle 32030 a, collectively considered a type of articulating deliveryor dispensing nozzle) is in the extended activated position as shown inFIG. 50B, fire suppression master node 50110 may send the appropriatecontrol signals to pump 32015 based on the particular shipping containermonitored that indicates there is an environmental anomaly warrantingsuch a mediation response by the fire suppression system 25010 a (e.g.,control signals from master node 50110 to pump 32015 to selectivelysupply fire suppression agent from chamber 32020 to needle 32030 a sothat the pressurized fire suppression agent is injected within shippingcontainer 24300 a). Thus, as shown in FIG. 50C, fire suppression agent32040 pressurized by pump 32015 (and, in some cases, pressurized asagent 32040 is stored within chamber 32020) may be supplied from firesuppression agent reservoir chamber 32020, then through needle 32030 bso that the agent enters shipping container 24300 a as a type ofmediation action or response that may be directly or indirectlyinitiated by the fire suppression system 25010 a (more particularly, bythe system's fire suppression master node 50110).

As shown in FIG. 50B, an embodiment of system 25010 a may have a part ofthe articulating delivery nozzle that is being inserted into shippingcontainer 24300 a deployed with one or more shipping container sensors(e.g., sensors 50010 on the delivery end portion 50005 of needle 32030a). Such shipping container sensors are operatively coupled (e.g., viawiring or via a wireless connection, such as with RF sensors) to thefire suppression master node 50110. As such, the insertion of a portionof needle 32030 a (including the delivery end 50005) into the shippingcontainer 24300 a allows for the fire suppression master node 50110 toexpand its available sensory input with which to monitor the interior ofthe shipping container 24300 a.

FIG. 51 provides further details regarding an embodiment of firesuppression system 25010 a where more shipping container sensors aredeployed that may assist with monitoring and further assessmentregarding any environmental anomaly detected relative to shippingcontainer 24300 a as well as refining how the system 25010 a mayadvantageously respond. Referring now to FIG. 51, further details areillustrated regarding the articulating delivery nozzle shown having beeninserted into shipping container 24300 a. The exemplary articulatingdelivery nozzle (as implemented in this embodiment with actuator 32025a, its related needle 32030 a, and apertures 50015 through which firesuppressant agent 32040 may flow), is equipped with shipping containersensors 50010 a on the delivery end portion 50005 of needle 32030 aalong with additional shipping container sensors 50010 b disposedelsewhere on needle 32030 a that are located below the shippingcontainer's housing (i.e., on a shaft of needle 32030 a where sensors50010 b are exposed to the interior of shipping container 24300 a oncethe needle 32030 a punctures shipping container 24300 a). Still furthershipping container sensors (not shown) may be deployed on needle 32030 aat one or more points that remain outside of the insertion point intothe shipping container 24300 a, but operate as exemplary shippingcontainer sensors coupled to the fire suppression master node andgenerating sensor data relevant to the area outside of the insertionpoint on the shipping container 24300 a. As noted above, these exemplaryshipping container sensors on the articulating delivery nozzle areoperatively coupled (e.g., via wiring or via a wireless connection, suchas with RF sensors) to the fire suppression master node 50110 so thatthe fire suppression master node 50110 may gather sensor data from suchshipping container sensors and use this sensor data in furtherassessments and actions to be taken related to a detected environmentalanomaly within shipping container 24300 a.

As shown in FIG. 51, exemplary fire suppression system 25010 a mayinclude additional shipping container sensors 50020 a, 50020 b disposedoutside the shipping container 24300 a being monitored. As shown in FIG.51, sensors 50020 a, 50020 b focus on the exterior of the shippingcontainer 24300 a so as to generate sensor data indicative of conditionson the exterior surface of shipping container 24300 a. As such, thisfurther type of sensor on system 25010 a may monitor the shippingcontainer 24300 a from the outside in conjunction with, for example,sensor-based ID nodes 1-6 within the shipping container, delivery enddisposed sensors 50010 a, and/or needle shaft disposed sensors 50010 b.Those skilled in the art will appreciate that such additional shippingcontainer sensors, while disposed on and as part of fire suppressionsystem 25010 a, provide the fire suppression master node 50110 morediverse sensing capabilities to better assess and respond to anydetected environmental anomaly within or related to shipping container24300 a.

In light of the above description of exemplary system 50000, includingdetails on exemplary fire suppression system 25010 a, an embodiment ofan improved system on a transit vehicle for coordinated mediation actionin response to an identified environmental anomaly on a shippingcontainer being transported by the transit vehicle can be described inmore detail as follows. This system embodiment generally includes atleast multiple wireless ID nodes (e.g., ID nodes 1-6) and a firesuppression system (e.g., fire suppression system 25010 a) that may bedisposed on a transit vehicle. The wireless ID nodes are disposed atdifferent locations within the shipping container (e.g., ID nodes 1-6shown in different locations within container 24300 a). Each of the IDnodes are at a low level of a hierarchical wireless node network and arerespectively configured and operative to broadcast signals over a firstwireless communication path. In some embodiments, the ID nodes may beimplemented as sensor-based wireless ID nodes (e.g., similar to thatexplained above with ID node 120 a in FIG. 3, as wells as each of IDnodes 1-6 that may have one or more sensors). Each of such ID nodes maygenerally include an ID node processor, ID node memory, at least oneenvironmental sensor, and a wireless radio transceiver. The ID nodememory is coupled to the ID node processor, and maintains at least an IDnode monitoring program code that provide programmatic functionality forthe sensor-based ID node when executed by the ID node processor. Theenvironmental sensor (such as a temperature sensor, a chemical sensor, apressure sensor, and the like) is configured to generate sensor datarelated to an environmental condition proximate the respective wirelessID node. The ID node's wireless radio transceiver is coupled to the IDnode processing unit and, for example, is configured to access thesensor data generated by the at least one environmental sensor andbroadcast the sensor data in response to a report command from the IDnode processor when the ID node processing unit executes the ID nodemonitoring program code.

The system's fire suppression system (e.g., exemplary fire suppressionsystem 25010 a) generally includes at least a fire suppressant materialreservoir (e.g., chamber 32020), a fire suppressant material pump (e.g.,pump 32015), an articulating delivery nozzle (e.g., actuator 32025 a andits related articulating needle 32030 a), and a wirelesstransceiver-based controller operating as a master node at a middlelevel of the hierarchical wireless node network (e.g., fire suppressionmaster node 50110). The fire suppressant material reservoir is a chamberor container that temporarily maintains a fire suppressant material. Insome embodiments, such material may be maintained under a storage levelof pressure so as to provide initial pressurized force with which thematerial exits the reservoir chamber (in addition to the or in place ofthe pump action). The fire suppressant material pump is connected to thefire suppressant material reservoir and responsive to a pump controlinput to activate pumping the fire suppressant material from the firesuppressant material reservoir. The articulating delivery nozzle isconnected to the fire suppressant material pump that receives the pumpedfire suppressant material and deploys from a retracted or defaultposition (e.g., as shown in FIG. 50A) to an extended position (e.g., asshown in FIGS. 50B and 50C) to deliver the fire suppressant material tothe shipping container. The wireless transceiver-based controller on thefire suppression system is implemented and operates as a master node(e.g., fire suppression master node 50110, which is an implementation ofexemplary master node 110) at a middle level of the hierarchicalwireless node network. The fire suppression system's master node isoperative to generate the pump control input and cause the articulatingdelivery nozzle to deploy and deliver the fire suppressant material tothe shipping container. Additionally, the master node of the firesuppression system is further configured to operate as a primary monitorfor the environmental anomaly by being operative to: (a) wirelesslymonitor the signals being broadcast from the ID nodes; (b) responsivelyidentify the environmental anomaly based upon the monitored signalsbroadcast from the ID nodes; (c) generate a layered alert notificationrelated to the environmental anomaly for the shipping container inresponse to identifying the environmental anomaly for the shippingcontainer (where the layered alert notification identifies a targetedmediation action and establishes a mediation response priority); and (d)initiate a mediation response by the fire suppression system related tothe targeted mediation action and the mediation response priority.

In one embodiment, the monitored signals from the ID node may notnecessarily include sensor data. As such, wirelessly monitoring thesignals being broadcast from the ID nodes; (b) responsively identifyingthe environmental anomaly based upon the monitored signals broadcastfrom the ID nodes by the master node may be based upon missing ID nodesthat appear to no longer be broadcasting. For example, the system's firesuppression master node may be further operative to responsivelyidentify the environmental anomaly based upon the monitored signalsbroadcast from the ID nodes by being operative to identity of theenvironmental anomaly for the shipping container when the signalsbroadcast from the ID nodes as wirelessly monitored by the master nodeindicate at least a threshold number of the wireless ID nodes are in astate of ceased broadcasting. Once a threshold number of ID nodes areidentified as no longer broadcasting, the master node in the firesuppression system may identify that an environmental anomaly exists andtake further steps to respond as noted above and below in furtherexamples and embodiments.

In another exemplary embodiment, when the system's ID nodes areimplemented as sensor-based ID nodes where each broadcasts sensor dataas part of the signals broadcast over the first wireless communicationpath, the system's master node of the fire suppression system may beprogrammatically configured to initiate the mediation response as partof (d) as a stepped mediation response that involves initiating a firststage response that further assesses the identified environmentalanomaly using the sensor data from at least one or more of the wirelessID nodes, and initiating a second stage response that causes deploymentof the fire suppressant material to the shipping container based uponand in response to the further assessment of the identifiedenvironmental anomaly in the first stage response. In more detail, themaster node of the fire suppression system may be programmaticallyconfigured to initiate the first stage response by being configured andoperative to detect sensor data from the monitored signals beingbroadcasted from the wireless sensor-based ID nodes; refine the identityof the environmental anomaly for the shipping container when thedetected sensor data does not include the sensor data from at least athreshold number of the wireless sensor-based ID nodes, and furtherrefine the identity of the environmental anomaly for the shippingcontainer when the detected sensor data indicates an environmentalcondition that exceeds an environmental threshold.

In another example, the fire suppression system may include shippingcontainer sensors (e.g., sensors 50010, 50010 a, 50010 b) coupled to themaster node. Such shipping container sensors provide sensor data to thefire suppression master node about the shipping container. As such, themaster node of the fire suppression system may be programmaticallyconfigured to be further operative to (d) initiate the mediationresponse as a stepped mediation response by being operative to (1)initiate a first stage response that further assesses the identifiedenvironmental anomaly using at least one or more of the shippingcontainer sensors, and (2) initiate a second stage response that causesdeployment of the fire suppressant material to the shipping containerbased upon and in response to the further assessment of the identifiedenvironmental anomaly in (1). In more detail, initiating the first stageresponse may have the fire suppression master node being configured andoperative to detect sensor data from the shipping container sensors(when the shipping container sensors, such as sensors 50020 a, 50020 b,are disposed outside the shipping container and focus on the exterior ofthe shipping container); and refine the identity of the environmentalanomaly for the shipping container when the detected sensor dataindicates an environmental condition that exceeds an environmentalthreshold.

In another embodiment, at least one or more of the shipping containersensors may be disposed on the articulating delivery nozzle (e.g.,sensor 50010 a or sensor 50010 b) so that when then the articulatingdelivery nozzle is disposed within the shipping container, thoseshipping container sensors are exposed to an interior of the shippingcontainer. As such, n the master node of the fire suppression system maybe programmatically configured to initiate the first stage response bydetecting sensor data from the at least one or more of the shippingcontainer sensors, and refining the identity of the environmentalanomaly for the shipping container when the detected sensor dataindicates an environmental condition that exceeds an environmentalthreshold. The detected sensor data from such shipping container sensorsmay, for example, include a detected temperature, a detected radiationlevel, or a detected chemical (such as CO or CO₂ disposed within theshipping container, a chemical indicative of an explosive within theshipping container, or a indicative of a fire within the shippingcontainer).

In a more detailed embodiment, the shipping container sensors may bedisposed on a delivery end of the articulating delivery nozzle (such assensor 50010 on delivery end 50005 of needle 32030 a). In such anembodiment, when then the articulating delivery nozzle is deployed withthe delivery end puncturing and disposed within the shipping container(e.g., as shown in FIG. 50B or 51), the shipping container sensors onthe delivery end are exposed to an interior of the shipping container.For example, as shown in FIG. 50B, sensors 50010 are exposed to theinterior of shipping container 24300 a when the delivery end 50005 ofarticulating nozzle 32030 a has punctured the housing of the shippingcontainer 24300 a. Likewise, as shown in FIG. 51, sensors 50010 a ondelivery end 50005 are exposed to the interior of shipping container24300 a when the delivery end of articulating nozzle 32030 a haspunctured the housing of the shipping container 24300 a.

In another embodiment, another combination of shipping container sensorsmay be used as part of the system. For example, a first portion of theshipping container sensors (e.g., sensors 50010 a, 50010 b) in thisembodiment may be disposed on the articulating delivery nozzle such thatwhen then the articulating delivery nozzle (e.g., collectively theactuator 32025 a that articulates needle 32030 a) is deployed within theshipping container, the first portion of the shipping container sensorsare exposed to an interior of the shipping container. In this example, asecond portion of the shipping container sensors (e.g., sensors 50020 a,50020 b) may be disposed outside the shipping container and focusing onthe exterior of the shipping container. In this configuration, thesystem's fire suppression master node may be programmatically configuredto initiate the first stage response by being configured and operativeto detect sensor data from the first portion of the shipping containersensors and the second portion of the shipping container sensors, andrefine the identity of the environmental anomaly for the shippingcontainer when the detected sensor data indicates an environmentalcondition that exceeds an environmental threshold. In this way, the firesuppression master node may rely upon differently disposed sensors otherthan the ID node sensors within the shipping container to initiate thefirst stage response.

In still another embodiment, three types of sensors may be used—namely,sensors in the ID nodes, shipping container sensors exposed to theinterior of the shipping container, and shipping container sensorsfocusing on the outside of the shipping container. For example, each ofthe system's wireless ID nodes may be implemented as a sensor-based IDnode operative to broadcast sensor data as part of the signals broadcastover the first wireless communication path. Additionally, a firstportion of the system's shipping container sensors may be disposed on adelivery end of the articulating delivery nozzle such that when then thearticulating delivery nozzle is deployed with the delivery endpuncturing and disposed within the shipping container, that portion ofthe shipping container sensors are exposed to an interior of theshipping container. Furthermore, a second portion of the system'sshipping container sensors may be disposed outside the shippingcontainer and focusing on the exterior of the shipping container. Assuch, the system's fire suppression master node may be programmaticallyconfigured to initiate the first stage response by being configured andoperative to: detect first sensor data from the first portion of theshipping container sensors; detect second sensor data from the secondportion of the shipping container sensors; detect third sensor data fromthe monitored signals being broadcasted from the wireless sensor-basedID nodes; and refine the identity of the environmental anomaly for theshipping container when a collective assessment of the first sensordata, the second sensor data, and the third sensor data indicates anenvironmental condition that exceeds an environmental threshold.

The system's master node may be further configured to operate as theprimary monitor for the environmental anomaly by being further operativeto (e) transmit the layered alert notification to a targeted mediationrecipient according to the mediation response priority. For example,such a targeted mediation recipient may be an external transceiver onthe transit vehicle (e.g., external transceiver 24150) having a display(e.g., a display in a cockpit or logistics support area of a transitvehicle 24200, such as display 40015) used by an operator of the transitvehicle that can alter movement of the transit vehicle or a logisticscrew member of the transit vehicle that can inspect the shippingcontainer.

The system's master node, in another example embodiment, may be furtherprogrammatically configured to identify the targeted mediation actionbased at least upon how many of the wireless ID nodes were not detected,and if that number of undetected wireless ID nodes was above a thresholdnumber of the wireless ID nodes. Having the current number of undetectedwireless ID nodes (i.e., those ID nodes no longer broadcasting signalsand in a state of ceased broadcasting) being above such a threshold mayallow the fire suppression master node to identify a particular targetedmediation action (e.g., automatically and immediately cause the firesuppression system to dispense the fire suppression agent, rather thancause a prompted mediation response message to be displayed to theoperator or crew of the transit vehicle requesting that the shippingcontainer be inspects or that the vehicle change course). In a furtherexample, the targeted mediation action identified by the master nodedepends upon what is loaded within the shipping container as indicatedby shipping information maintained on the master node of the firesuppression system. In another example, the master node may be furtherprogrammatically configured to identify the targeted mediation actionbased upon at least one of (a) how many of the wireless ID nodes werenot detected as broadcasting above the threshold number of the wirelesssensor-based ID nodes and (b) how much an environmental condition (basedon sensor data from the ID nodes) exceeds the environmental threshold.This may also depend upon what is loaded within the shipping containeras indicated by shipping information maintained on the master node ofthe fire suppression system.

In a further example of such a system embodiment, the master node may befurther programmatically configured to automatically establish themediation response priority based upon at least one of (a) how many ofthe wireless ID nodes were not detected as still broadcasting above thethreshold number of the wireless ID nodes and (b) how much theenvironmental condition exceeds the environmental threshold. Forinstance, the established mediation response priority may be a highpriority level indicating further travel by the transit vehicle is to beat least minimized as part of the mediation response or, for example, anintermediate priority level indicating further travel by the transitvehicle is permissible as part of the mediation response.

In still another example of such a system embodiment, the master nodemay adjust how the ID nodes broadcast. In one example, the master nodemay be further operative to wirelessly monitor the signals beingbroadcast from the ID nodes by being operative to: detect the signalsbroadcasted by the wireless ID nodes according to a broadcast profilemaintained by each of the wireless ID nodes (e.g., broadcast profileinformation as part of profile data 330 that defines a first messagingrate used to regulate how often the signals are broadcast from an IDnode to the master node (where the first messaging rate is higher than adefault messaging rate)); and instruct each of the wireless ID nodes tobroadcast future signals at a second messaging rate that exceeds thefirst messaging rate after initiating the mediation response. In moredetail, the master node may instruct each of the wireless ID nodes tochange from the default messaging rate to the first messaging rate(e.g., an initial messaging rate value correlated to an environmentalrisk associated with material maintained within the shipping container).Thus, for more volatile or risky materials within a particular shippingcontainer, the master node may have a higher or faster messaging ratethan normal so as to keep closer tabs on the material and stay situatedto more rapidly and robustly provide an immediate and tailored mediationresponse to address any detected environmental anomaly.

In another example (where the ID nodes broadcast generated orshared/acquired sensor data), the master node may be further operativeto detect the sensor data from the monitored signals being broadcastfrom the wireless sensor-based ID nodes by being operative to: detectthe sensor data broadcasted by the wireless sensor-based ID nodesaccording to a broadcast profile maintained by each of the wirelesssensor-based ID nodes (e.g., broadcast profile information as part ofprofile data 330 that defines a first messaging rate used to regulatehow often the signals are broadcast from an ID node to the master node(where the first messaging rate is higher than a default messagingrate)); and instruct each of the wireless sensor-based ID nodes tobroadcast future generated sensor data at a second messaging rate thatexceeds the first messaging rate after initiating the mediationresponse. In more detail, the master node may instruct each of thewireless ID nodes to change from the default messaging rate to the firstmessaging rate (e.g., an initial messaging rate value correlated to anenvironmental risk associated with material maintained within theshipping container).

In a further example, the fire suppression master node may be furtherprogrammatically configured to operate as a primary monitor for theenvironmental anomaly by being further operative to receive an alteredtrigger limit related to the targeted mediation action and initiate themediation response using the altered trigger limit related to thetargeted mediation action. Such a trigger limit may take the form of alimit or threshold used to identify the environmental anomaly whencompared to monitored signals broadcast from the ID nodes. Such analtered trigger limit may come from, for example, the externaltransceiver on the transit vehicle (e.g., as defined by an operator ofthe transit vehicle using the external transceiver or a logistics crewmember of the transit vehicle using the external transceiver or asprovided to the external transceiver of the transit vehicle from aremote control center in communication with the external transceiver).

Further still, another embodiment may have the master node beingconfigured to receive a request to initiate a secondary mediationresponse by the fire suppression system related to the targetedmediation action and the mediation response priority. Such a request maybe provided to the master node from the external transceiver in responseto the layered alert notification. For example, the master node 50110 inthe fire suppression system 25010 a may provide an immediate and quickinitial mediation response, but after an inspection prompted by thetransmitted layered alert notification, the external transceiver 24150may receive input from a crew member via the display or user inputinterfaces that responsively sends a request to fire suppression masternode 50110 for a secondary mediation response (e.g., additional firesuppressant agent material to be dispensed into shipping container 24300a).

While the system embodiment above is explained using an exemplary firesuppression system 25010 a, a further system embodiment may use analternatively configured fire suppression system 25010 b as shown inFIG. 52 with similar functionality as the system embodiment describedabove, but using a pressurized fire suppression material container 52005and a controlled release nozzle 52010 instead of an articulatingdelivery nozzle that may puncture the shipping container and haveshipping container sensors disposed on that articulating deliverynozzle. As such, similar system functionality as described in thevarious embodiments above (e.g., such as that described and supported byFIGS. 50A-50C and 51) will also apply to the embodiment shown in FIG.52.

In more detail and referring now to FIG. 52, exemplary system 52000 hasexemplary fire suppression system 25010 b disposed on transit vehicle24200 transporting shipping container 24300 a. The fire suppressionsystem 25010 b generally includes pressurized fire suppressant materialcontainer (e.g., chamber or container 52005), a fire suppressantmaterial pump (e.g., pump 32015), a controlled or actuated releasenozzle (e.g., having an electronically controlled release valve toselectively open and close), and a wireless transceiver-based controlleroperating as a master node at a middle level of the hierarchicalwireless node network (e.g., fire suppression master node 50110) thatperforms the similar primary monitor functions as described above. Inmore detail, the exemplary release nozzle 52010 on fire suppressionsystem 25010 b is operatively coupled to the pressurized firesuppressant material container 52005 so that nozzle 52010 may providefire suppressant material to shipping container 24300 a. Nozzle 52010may include an electronically activated valve that selectively opens inresponse to an activation input signal from fire suppression master node50110 in order to control the flow of the fire suppressant material fromthe pressurized fire suppressant material container (via pump actionshould an embodiment of fire suppression system 25010 b include pump32015 or via pressurized release/gravity when no pump is implemented onan embodiment of fire suppression system 25010 b) so that the firesuppressant material may be delivered to the shipping container 24300 a.As such, those skilled in the art will appreciate that further examplesof system 52000 shown in FIG. 52 may substitute pressurized firesuppression material container 52005 with a non-pressurized containerfor the fire suppression agent.

Enhanced Container for Rapid Environmental Anomaly Response & FireSuppression

Still further embodiments addressing shipping container environmentalanomalies include another type of enhanced shipping container improvedto have integrated fire suppression materials and panels as part of thecontainer itself and systems using such enhanced shipping containers. Ingeneral, an exemplary embodiment of such an enhanced shipping containermay have one or more added or integral fire suppression panels that arepart of or attached to one or more internal parts of the container (suchas a top portion (e.g., lid, ceiling, cap, roof) or wall). The firesuppression panels have internal exposure, are engineered to melt due tohigh heat, and quickly release an amount of fire suppression material.This may be considered an initial or first type of mediation response,and may be coordinated with ID node monitoring within the shippingcontainer, so that an external fire suppression system has more time topunch through the container and have a secondary release of additionalfire suppression material. Such an enhanced shipping container havingone or more fire suppression panels provides a vessel for transportingitems, objects, or packages that can, by its structural design, halt orminimize an environmental anomaly (such as a fire) within that transportvessel.

While some embodiments may have a single enhanced shipping containerwith one or more fire suppression panels designed to distribute the firesuppression material contained or simply that are part of such firesuppression panels, a further embodiment may deploy such enhancedcontainers in a nested fashion. More specifically, a further embodimentmay have a shipping container enhanced with one or more integral firesuppression panels where the container encompasses another enhancedcontainer with further fire suppression panels. Still furtherembodiments may use multiple layers of fire suppression panels as acomposite or collective panel for a particular shipping container sothat the distributed release of fire suppression material may be stagedas the interior exposed temperature sensitive material of each differentlayer reaches its respective melting point to release and distribute itsrespective amount of fire suppression material.

FIGS. 53A-53D are a series of diagrams of exemplary shipping containersthat may be deployed in accordance with an embodiment of the inventionas having one or more fire suppression panels. Referring now to FIG.53A, exemplary shipping container 53300 a is shown in perspective(similarly disposed as described above with respect to exemplaryshipping container 24300 a) as generally having a container base portion53005 a, multiple container walls 53010 a vertically disposed relativeto the base 53005 a, a container top portion 53015 a, and a resealableaccess closure 53020 a (e.g., a door, hatch, screen, webbing, and thelike) on one of the walls 53010 a providing selective access to withinthe container 53300 a. The container base portion 53005 a may supportany packages that are maintained within container 53300 a. As shown inFIG. 53A, the walls 53010 a generally having one edge coupled to thecontainer base 53005 a and another edge coupled to the top or lid 53015a (as well as the other edges being coupled to other walls). In thisconfiguration, the container base 53005 a, the container walls 53010 a,and the container top 53015 a collectively define an interior storagespace of container 53300 a, which may maintaining packages being shipped(e.g., items, assets, objects whether enclosed in packaging material ornot).

In general, an exemplary shipping container's base, walls, and top maybe separate structural elements of the container that are attached toeach other (e.g., welded, bolted, molded, screwed, glued, or other wisedmade to be fixed relative to each other), but such elements of thecontainer may also be part of a singular integrated container. Forexample, the shipping container may have a base, walls, and a top whilesuch structural elements are portions of a singular enclosing structurethat defines the interior storage space of the container. In otherwords, some of the container's base, walls, and a top may be integratedto each other as part of the same enclosing structure (e.g., walls andbase, walls to each other, walls to the container top).

Another embodiment of an exemplary shipping container that may bedeployed with fire suppression panels may have a base and one or morewalls, but not include a top and may not fully enclose to form a sealedunit. As such, this type of shipping container may still have aninterior storage space relative to above the base and next to the wallswhere packages may be maintained as supported by the base while havingless than a fully encompassing enclosure structure to seal off theshipping container. Those skilled in the art will appreciate that thewall may have one or more integrated or attached fire suppression panelsas described in more detail below.

As shown in FIG. 53A, the resealable access closure 53020 a on one ofthe walls 53010 a provides selective access to within the container53300 a. Such a closure may be implemented with a rigid door on hingeswith a handle and lock, but other exemplary closures may take the formof a flexible structure (e.g., thick plastic sheet, webbing, reinforcedscreens, and the like) that may be selectively released to gain accessto within the container 53300 a and then secured in place to helpprevent contents (e.g., packages) from falling out of the container53300 a.

FIG. 53B illustrates an alternative embodiment an exemplary shippingcontainer more in the form of a unit load device (ULD) type ofcontainer. Such a ULD container is commonly used to transport items onaircraft as the container's physical configuration is adapted to makebetter use of available cargo space onboard the aircraft. Referring nowto FIG. 53B, exemplary shipping container 53300 b is illustrated withsimilar features that that shown for shipping container 53300 a, butwith a modified wall that includes a vertical top wall portion 53025 andan angled bottom wall portion 53030. Those skilled in the art willappreciate that the remaining base 53005 b, walls 53010 b, top portion53015 b, and resealable access closure 53020 b as shown on exemplaryshipping container 53300 b are similar to the corresponding parts ofshipping container 53300 a described above.

While the exemplary shipping container 53300 b shown in FIG. 53B istypically targeted for use on wide-body aircraft, where two of suchcontainers may be deployed to span the cargo width of the aircraft(where the each container's modified wall extends towards outward theaircraft fuselage), a further embodiment of an exemplary shippingcontainer 53300 c is shown in FIG. 53C may be one used in cargo areas onnarrower aircraft. As shown in FIG. 53C, exemplary shipping container53300 c has two sides with modified walls (e.g., a first modified wallhaving a vertical top wall portion 53025 c and an angled bottom wallportion 53030 c and a second modified wall, on the opposing side of thecontainer, having a similar vertical top wall portion 53035 and asimilar angled bottom wall portion 53040. As such, certain walls onexemplary shipping containers (such as containers 53300 b and 53300 c)may not be simply vertical walls, but may include multiple wall panelsor portions that make up the walls and that function to help enclose thecontainer and define the interior storage space of the container.

FIG. 53D illustrates the interior storage space on exemplary shippingcontainer 53300 c. Referring now to FIG. 53D, shipping container 53300 chas its resealable access closure 53020 c (e.g., door or hatch) in anopen position showing the interior storage space where items may bemaintained. Such items, for example, may include packages (e.g., objectsand items whether enclosed in packaging materials or not), exemplarywireless ID nodes that may broadcast wireless signals, and command nodesthat may monitor those wireless signals and initiate mediation responseswhen detecting an environmental anomaly based upon such monitoring.

As generally mentioned above, an exemplary shipping container (such asthose described in each of FIGS. 53A-53D) may be enhanced and improvedwith one or more added or integral fire suppression panels that are partof or attached to one or more internal parts of the shipping container.In generally, exemplary fire suppression panels may be located on one ormore of the container's top portion (e.g., lid, ceiling, cap, and roof)or any wall (including any resealable access closure that is consideredpart of a wall). An exemplary fire suppression panel is generallydisposed (whether integrated into or attached such parts of the shippingcontainer) so as to have internal exposure to the interior storage areaof the shipping container. As composed, an exemplary fire suppressionpanel is deployed so as to have its interior facing surface designed soas to purposefully melt due to high heat conditions within the interiorstorage area of the shipping container (due to an environmental anomaly)and so that the panel may release or distribute an amount of firesuppression material maintained behind the interior facing surface as aresult.

FIGS. 54 and 55 provide further details on different embodiments ofexemplary fire suppression panels. In particular, FIG. 54 is a diagramillustrating an exemplary shipping container enhanced with an exemplaryfire suppression panel implemented as being integrated as part of orwithin at least part of a shipping container's walls in accordance withan embodiment of the invention. Referring now to FIG. 54, exemplaryshipping container 53300 a is illustrated in cross section showingdetails of an exemplary fire suppression panel 54000 integrated as partof one of the container's walls 53010 a. In more detail and as shown inFIG. 54, exemplary fire suppression panel 54000 is shown as having asupport sheet 54005 made from a fire resistant material and an interiorexposed sheet 54010 made from a temperature sensitive material. Supportsheet 54005 provides integral structural support for the wall 53010 a(or for the top portion 53015 a if disposed on such a part of theshipping container 53300 a) in a manner that allows for structuralintegrity of the container 53300 a even if the interior exposed sheet54010 is not present (e.g., has melted, at least in part, as designed todo when exposed to high heat from a fire or explosive event). A sealedboundary 54015 connects the support sheet 54005 and the interior exposedsheet 54010 on peripheral edges of each of the support sheet 54005 andthe interior exposed sheet 54010 in a way that the combination of thesealed boundary 54015, the support sheet 54005, and the interior exposedsheet 54010 define a holding cavity within which integrated firesuppressant agent material 54020 may be kept. Such material 54020 (alsoreferred to as fire suppression material) is released or distributedinternally when the temperature sensitive material of the interiorexposed sheet 54010 has melted or given way in the face of anenvironmental anomaly (e.g., heat from a fire, explosion, or heat causedby a chemical reaction or condition) within the container 53300 a. Inother words, the temperature sensitive material of the interior exposedsheet 54010 purposefully releases the integrated fire suppressantmaterial 54020 from within the holding cavity when the temperaturesensitive material of the interior exposed sheet 54010 is exposed to athreshold temperature (e.g., a melting point temperature for thetemperature sensitive material) and, thus, distributes the integratedfire suppressant material 54020 within the holding cavity as that cavityis no longer contained under the conditions of the environmentalanomaly. In more detail, the temperature sensitive material of theinterior exposed sheet 54010 releases the integrated fire suppressantmaterial 54020 from within the holding cavity and operates as apurposefully designed heat sensitive aperture to the holding cavitymaintaining the integrated fire suppressant material 54020. Thispurposeful release occurs as intended when the temperature sensitivematerial melts due to a heat environment that exceeds the thresholdtemperature. The resulting release of the integrated fire suppressantmaterial 54020 is into the interior storage space and may be releasedonto at least a portion of the packages maintained within the container53300 a.

While FIG. 54 illustrates exemplary sealed boundary 54015 (e.g., asealed edge or frame for panel 54000) as a separate structure from thewall 53010 a, those skilled in the art will appreciate that sealedboundary 54015 may be implemented to include part of the wall (or topportion) where that part of the container abuts each of support sheet54005 and interior exposed sheet 54010 on their respective peripheraledges and that part of the container works with support sheet 54005 andinterior exposed sheet 54010 to seal and contain the integrated firesuppressant agent material 54020. Furthermore, exemplary integrated firesuppression panel 54000 may be implemented as part of as other wallsshown on container 53300 a, or as part of or as the top portion 53015 ashown on container 53300 a. Additionally, an embodiment may deploymultiple integrated fire suppression panels on different parts ofcontainer 53300 a, such as integrated into cutout or recessed portionsof a container's walls 53010 a or top/lid/ceiling portion 53015 a.

Further embodiments may deploy multiple integrated fire suppressionpanel layers where each layer has a temperature sensitive sheet that isinternally exposed. The outer most layer may include a support sheet,but each of the other layers moving inward may essentially includelayers of fire suppressant agent material and temperature sensitiveinterior exposed sheets where each layer may have a common designedtemperature melting point or, alternatively, have the interior exposedsheet of each successive layer having different temperature meltingpoints so as to further stage the release of the layers of firesuppressant agent material.

Those skilled in the art will appreciate the while an integrated firesuppression panel, such as panel 54000, may take the form of a largerpanel of the interior exposed temperature sensitive sheet, furtherembodiments may deploy the panel as having the interior exposed sheetmade from similar material as that of the outer support sheet, but withone or more apertures forming essentially one or more release pointswith temperature sensitive layers disposed within the apertures. Whenthe temperature sensitive layer disposed within the apertures areexposed to their designed melting point, the fire suppressant materialcontained behind such temperature sensitive layers may be releasethrough the apertures (e.g., a pressurized release of the firesuppressant material through multiple different apertures on theinternal side of the fire suppressant panel).

FIG. 55 is a diagram illustrating an exemplary shipping containerenhanced with an alternative exemplary fire suppression panel 55000attached to one of the container's walls 53010 a in accordance with anembodiment of the invention. Referring now to FIG. 55, a cross sectionalview of a similar exemplary fire suppression panel 55000 that may beseparate from the wall 53010 a or top/ceiling portion 53015 a ofcontainer 53300 a, but attached to any of the interior surfaces of thewalls or ceiling to provide an additional fire suppression measure. Asshown in FIG. 55, exemplary attached fire suppression panel 55000 issimilarly composed as panel 54000 in that is includes a support sheet55005 made from a fire resistant material (where the support sheet isattached in this embodiment to the interior surface of wall 53010 a), aninterior exposed sheet 55010 made from a temperature sensitive materialas described above, and a sealed boundary 55015 connecting the supportsheet 55005 and the interior exposed sheet 55010 on peripheral edges ofeach of the support sheet 55005 and the interior exposed sheet 55010(where the combination of the sealed boundary 55015, the support sheet55005, and the interior exposed sheet 55010 defines a holding cavity fortemporarily maintaining integrated fire suppression material 55020 thatoccupies the holding cavity within the fire suppression panel 55000).Similar to that described above for exemplary integrated firesuppression panel 54000, the temperature sensitive material of theinterior exposed sheet 55010 releases the integrated fire suppressantmaterial 55020 within the holding cavity when the temperature sensitivematerial of the interior exposed sheet 55010 is exposed to a thresholdtemperature (such as that generated from an environmental anomaly, e.g.,a fire, an explosion, a chemical leak, and the like). In more detail,the temperature sensitive material of the interior exposed sheet 55010of the attached fire suppression panel 55000 may release and distributethe integrated fire suppressant material 55020 held within the holdingcavity when the temperature sensitive material melts when exposed to thethreshold temperature or when the temperature sensitive materialreleases the integrated fire suppressant material in response to abreakdown of the temperature sensitive material due to a heatenvironment that exceeds the threshold temperature. Such a designedrelease of the integrated fire suppression material 55020 into theinterior storage space of container 53300 a may be onto at least aportion of the packages near the fire suppression panel depending onwhat has been loaded within the container 53300 a and where suchpackages are within the container.

Further examples may have the integrated fire suppressant material 55020maintained within the holding cavity under pressure so that as any ofthe temperature sensitive material of the interior exposed sheet 55010melts or gives way as it is designed to do, the pressurized firesuppressant material 55020 is expelled from the holding cavity at thatpoint for enhanced distribution onto at least a portion of the packagesnear the fire suppression panel.

A further example may have the interior exposed sheet 55010 made ashaving apertures in the sheet and where the only temperature sensitivematerial in sheet 55010 is disposed within such apertures (e.g.,temperature sensitive plugs in each of a series of distributed aperturesat different locations on the interior exposed sheet 55010). In thisway, an embodiment of fire suppression panel 55000 may hold firesuppressant material 55020 under pressure between support sheet 55005and the aperture laden interior exposed sheet 55010 where each apertureis temporarily plugged with temperature sensitive material that maypurposefully give way at a predetermined pressure to release the firesuppressant material 55020 while enhancing the structural support of thepanel (given the entire interior exposed sheet would not give way inthis embodiment).

While only one attached fire suppressant panel 55000 is shown in FIG.55, further embodiments may deploy multiple attached fire suppressionpanels disposed on different parts of container 53300 a, such as fixedto or attached to one or more locations on the container's walls 53010 aor top/lid/ceiling portion 53015 a. In still further embodiments, theattached fire suppressant panel or panels maybe fixed to or removablymounted within cutout or recessed portions of the container's walls53010 a or top/lid/ceiling portion 53015 a so as to provide replaceablepanels that may be dynamically staged and placed into different targetedparts of the container depending on the character and nature of what maybe transported within the container and where such material (e.g.,packages with such material) is loaded within the container.

Enhanced shipping containers deployed with either integrated or attachedfire suppression panels (such as panels 54000 and 55000) may beincorporated into systems that use a network of wireless nodes (such asID nodes and command nodes) to detect an environmental anomaly relatedto the shipping container and respond with multiple mediation responses.FIGS. 56A-56D are a series of diagrams illustrating details of andoperations involving an enhanced shipping container having at least onefire suppression panel and as used in an improved system for coordinatedmediation action in response to an identified environmental anomalyrelated to the shipping container in accordance with an embodiment ofthe invention. Referring now to FIG. 56A, system 56000 is illustratedwith similar components as shown in FIG. 44. However, shipping container24300 a shown in FIG. 44 is replaced with exemplary enhanced shippingcontainer 56300 shown in FIGS. 56A-56D as part of system 56000. In moredetail, exemplary shipping container 56300 is shown having a containerbase portion 41005 that may support packages loaded within container56300, and an enclosing structure coupled to the container base portion(e.g., walls 41010 and top portion 41015). Such enclosing structure andthe container base portion 41005 define an interior storage space formaintaining any packages loaded within container 56300.

Notably, at least a part of the enclosing structure includes a firesuppression panel 56005 disposed to the interior storage space of thecontainer. The fire suppression panel 56005 as noted above, may beintegrated as part of the enclosing structure (e.g., one of the walls41010) or simply attached to the interior of the enclosing structure(e.g., attached to a recessed area on one of the walls 41010). Asdisposed relative to the enclosing structure of container 56300, firesuppression panel 56005 having temperature sensitive material on aninterior exposed surface of the fire suppression panel (e.g., aninterior exposed sheet as described above relative to exemplary panels55000, 56000). The fire suppression panel 56005 internally containsintegrated fire suppression material (such as material 54020, 55020)next to the temperature sensitive material on the interior exposedsurface. As such, the temperature sensitive material on the interiorexposed surface of panel 56005 will fail to contain the integrated firesuppressant material within the fire suppression panel 56005 when thetemperature sensitive material is exposed to a threshold temperature(e.g., heat that exceeds the threshold temperature from a fire withinthe container 56300, from an explosion within the container 56300, orfrom a chemical condition or reaction that generates such heat withinthe container 56300).

Exemplary shipping container 56300 shown in FIG. 56A also includesmultiple wireless sensor-based ID nodes 1-10 (also referenced as 24120a-24120 j, respectively) disposed at different locations within theenhanced shipping container 56300 and a command node 24160 mounted tothe shipping container 56300 (e.g., fixed or removably attached to theceiling within shipping container 56300). ID nodes 1-2 are disposedalong the ceiling on the top 41015 of container 56300, ID nodes 3-6 aredisposed along the base 41005, and ID nodes 7-10 are disposed along thewalls 41010 of container 56300. While not shown as being associatedwith, packed into, affixed to, or traveling with any particular package,those skilled in the art will appreciate in light of the descriptionabove that embodiments may deploy particular ID nodes on or integral toparts of the container, any package with in the container, or freelydisposed within the container without being fixed to, attached, orassociated with any particular package or particular part of thecontainer. Each of ID nodes 1-10 are at a low level of a hierarchicalwireless node network, where command node 24160 is disposed at a middlelevel of such a network (and where further elements, such as externaltransceiver 24150 and remote server 24100 are disposed higher within thenetwork) and each of the ID nodes are respectively configured andoperative to broadcast signals that may be received by command node24160.

Similar to that described above, command node 24160 has at least aprocessor, a memory coupled to the processor, and a dual transceivercommunication interface that is configured to communicate with ID nodes1-10 as well as communicate with external transceiver 24150 and onboardfire suppression system 25010. As deployed as part of system 56000, thecommand node's memory includes a command node container managementprogram code (e.g., code 26425). In this particular embodiment asillustrated in FIG. 56A-56D, the processor on command node 24160executes the command node container management program code, which thenprogrammatically configures the processor on command node 24160 to bespecially operative to detect the sensor data broadcasted from thesensor-based ID nodes 1-10 using one of the communication interfaces onthe command node 24160; responsively identify the environmental anomalyfor the shipping container 56300 (e.g., a fire 56010 within container56300 shown in FIG. 56B) when the detected sensor data indicates releaseof the integrated fire suppression material 56020 from the firesuppression panel 56005 as a first level mediation response (as shown inFIG. 56C); generate a layered alert notification related to theenvironmental anomaly for the shipping container in response toidentifying the environmental anomaly for the shipping container(wherein the layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority; and cause the command node's communicationinterface to transmit the layered alert notification to the externaltransceiver 24150 to initiate a secondary mediation response related tothe targeted mediation action.

As part of this system embodiment, the command node's processor may beprogrammatically configured to be operative to also identify theenvironmental anomaly for the shipping container 56300 when the detectedsensor data indicates at least one of (a) when the detected sensor datadoes not include the sensor data from at least a threshold number of thesensor-based ID nodes; and (b) when the detected sensor data indicatesan environmental condition that exceeds an environmental threshold.

Furthermore, the secondary mediation response may, for example, beimplemented as causing the external transceiver 24150 to generate asecondary mediation response notification for an operator of the transitvehicle as the targeted mediation recipient (e.g., a prompt message forsuch an operator on a display of the external transceiver where such aprompt message requests the operator of the transit vehicle to altermovement of the transit vehicle). In another example, the secondarymediation response may be causing the external transceiver 24150 togenerate a secondary mediation response notification for a logisticscrew member of the transit vehicle as the targeted mediation recipient(e.g., a prompt message for such a crew member on a display of theexternal transceiver where such a prompt message requests the logisticscrew member to inspect the enhanced shipping container). In stillanother example, the secondary mediation response may be causing theexternal transceiver to generate a secondary mediation responsenotification that activates fire suppression system 25010 within thetransit vehicle 24200 and outside the enhanced shipping container 56300.In response, the fire suppression system 25010 operates as the targetedmediation recipient to dispense additional fire suppression material32040 within the enhanced shipping container as the secondary mediationresponse related to the targeted mediation action. In anotherembodiment, the command node itself is operative to directly initiatethe secondary mediation response by directly activating fire suppressionsystem 25010, which then responsively punctures container 56300 andinjects additional pressurized fire suppressant material 32040 from firesuppression system 25010 as shown in FIG. 56D.

A further extension of such a system embodiment may expressly includethe fire suppression system, such as system 25010, as a further elementof the system that includes supplemental fire suppressant material34020; a delivery nozzle 32030 a that deploys to deliver thesupplemental fire suppressant material to within the enhanced shippingcontainer 56300, and a fire suppressant pump (such as pump 32015) thatactivates to cause the supplemental fire suppressant material 32040 toflow through the delivery nozzle 32030 a and into shipping container56300. As such, this system's command node processor may then beprogrammatically further operative to cause one of its communicationinterfaces to transmit the layered alert notification to the externaltransceiver 24150 to activate the fire suppression system 25010 todispense the supplemental fire suppression material 32040 as a secondarylevel mediation response related to the targeted mediation action.Alternatively, this system's command node processor may beprogrammatically further operative to cause one of its communicationinterfaces to transmit the layered alert notification directly to thefire suppression system 25010 (without involving external transceiver24150) to dispense the supplemental fire suppression material 32040 as asecondary level mediation response related to the targeted mediationaction.

Node Enhanced Battery, Battery Packs, and Battery Packages

Additional embodiments may provide further improvements to environmentalanomaly detection and mediation responses using enhanced sensor-basednodes (such as sensor-based ID nodes) that may be directly incorporatedinto, disposed as part of, or otherwise associated with a battery (suchas a lithium-based or lithium-ion battery), pack of batteries, orbattery packaging so as to enable integrated environmental anomalydetection and reporting at that low level of a wireless node network.For example, travel suit cases may have internal batteries that offer alevel of convenience to a traveler by allowing the traveler to charge apersonal device (e.g., smartphone, laptop, tablet) while that device issecured within the suit case. And while this may be a convenience to thetraveler, such a charging situation may create a overheating situationresulting in a type of environmental anomaly unintended by the travelerbut potentially catastrophic in the context of occurring while on anaircraft carrying other travelers, crew, and cargo. The ability to use anode-enhanced battery in such a situation allows for advantageousmonitoring for environmental anomalies in an advantageous and novelmanner (e.g., by a vehicle master node (or aircraft master node) thatmonitors sensor data from different node-enhanced batteries on board theaircraft and provides alert notifications to flight personnel relativeto potential dangers, such as overheating of particular batteries duringuse on the aircraft or overheating of particular batteries when simplystored on the aircraft).

Exemplary embodiments may have an associated sensor-based ID node beingdisposed and operative to sense and communicate the battery's chargestatus and/or temperature at one or more locations of the battery,battery pack, or packaging of such a battery or group of batteries. Sucha sensor-based ID node may be associated with the battery (its parts orwith multiple batteries) as, for example, an integrated assembly of thesensor-based ID node and the battery (or its parts or with the group ofbatteries) where the ID node may not be separable from the assembly andmay also be powered by the battery it may be monitoring. Another examplemay have the sensor-based ID node as a separate device (with or withoutits own power supply), but still being integrated with the battery it isassociated with for monitoring purposes. Still another example may havethe sensor-based ID node as a removable device with its own power supplyand that is externally attached to the battery (its parts or withmultiple batteries) to be monitored but in a manner that has thesensor-based ID node as a replaceable or swappable device relative tothe battery.

Self-sensing in this manner can advantageously activate the ID node(even if in a low power mode) to cause the generation and transmissionof a relevant alert notification that depends on the temperature and/orbattery status to intelligently initiate mediation responses. In someembodiments, the battery package may include multiple ID nodes, multiplesensors with a single ID node, or involve a network of a master node(e.g., a command node, such as exemplary command node 24160) and severalID nodes as part of the package depending on the size and type ofbattery package. Embodiments may have the ID nodes maintain data thatidentifies the specific associated battery or batteries, as well as thetype or characteristic category of such batteries, where suchinformation may be used as part of determining a relevant andappropriate mediation response.

FIG. 57 is a diagram illustrating an exemplary node-enabled batterysystem having integrated environmental detection and reportingfunctionalities in accordance with an embodiment of the invention.Referring now to FIG. 57, an exemplary node-enhanced battery system57000 (NEB, also referenced as a node-enabled battery system) is shownhaving a battery 57002, such as a lithium-ion battery. Those skilled inthe art will appreciate that battery 57002 may comprise a housing andmultiple battery cells that are commonly coupled to form a power source.In other words, the battery 57002 may have multiple battery packs basedupon different battery cells (e.g., lithium battery cells). A terminalpart of such a battery 57002 includes battery terminal connections57005, 57010 through which electricity may be made available to tap intothe power source of battery 57002.

Exemplary system 57000 further includes a sensor-based ID node 24120 aattached to the battery 57002. As shown in FIG. 57, ID node 24120 a ismounted on the battery 57002, but further implementations may attach IDnode 24120 a in a manner that incorporates the ID node 24120 a into thephysical structure of the battery 57002 (e.g., integrates ID node 24120a as part of battery 57002). Exemplary sensor-based ID node 24120 a(e.g., an implementation of ID node 120 a explained above and withreference to FIG. 3) includes a node processor, a node memory storagecoupled to the node processor, a wireless communication interfacecoupled to the processor, as well as one or more sensors coupled to theprocessor. The node memory storage maintains at least a batterymonitoring program code and a battery threshold metric value (e.g., aspart of the node control and management code 325 stored on memory 320 ofID node 120 a). The wireless communication interface (e.g., variablepower short range communication interface 375) may be a low powercommunication interface capable of Bluetooth Low Energy formattedcommunications. The sensor(s) deployed as part of sensor-based ID node24120 a is generally operative to sense a battery status condition forthe battery 57002. Such a sensor (e.g., sensor 360) may be integratedand deployed with ID node 24120 a, but may be remotely disposed (e.g.,sensors 57360 a-57360 g) at different locations on the battery 57002(e.g., sensor 57360 a disposed at the terminals 57005, 570010 to sensethe charge status condition of the battery 57002; sensors 57360 b-57360g disposed on dispersed and different locations on the housing of thebattery 57002). Further embodiments may have the sensor or sensorsdisposed within battery 57002 to detect a charge status condition ortemperature, for example, from within battery 57002.

As part of system 57000, the processor of sensor-based ID node 24120 ais programmatically configured, when executing the battery monitoringprogram code, to be operative to receive status data from the sensor(where the status data reflects the battery status condition as sensedby the sensor); automatically trigger generation of a layered alertnotification related to the battery when the received status data isinconsistent with the battery threshold metric value; and cause thewireless communication interface to broadcast the layered alertnotification to initiate a mediation response related to the batterystatus condition for the battery.

In more detail, the battery status condition sensed by the sensor on thesensor-based node may be a charge status condition of the battery (e.g.,a voltage level indicative of the charge status of battery 57002). Assuch, the node processor may be programmatically configured to beoperative to automatically trigger generation of the layered alertnotification (a) when the battery threshold metric value is a thresholdvoltage value and (b) when the received status data on the charge statuscondition of the battery is less than that threshold voltage value.

In another example, the battery status condition sensed by the sensor onthe sensor-based node on battery 57002 may be a temperature condition ofthe battery. As such, the node processor may be programmaticallyconfigured to be operative to automatically trigger generation of thelayered alert notification (a) when the battery threshold metric valueis a threshold temperature value and (b) when the received status dataon the temperature condition of the battery exceeds that thresholdtemperature value.

As noted, exemplary sensor-based ID node 24120 a is shown equipped withmultiple battery sensors 57360 a-57360 g disposed on different points ofthe battery 57002. In this configuration, an embodiment may have thebattery status condition sensed by each of the battery sensors beingtemperature conditions of the battery 57002, where each of thetemperature conditions corresponds to the respective different point on(or in) the battery 57002 where the respective battery sensor isdisposed. As such, the node processor on ID node 24120 a may beprogrammatically configured to be operative to receive the status databy receiving individual status information from each of the batterysensors as the status data. Furthermore, the node processor may beprogrammatically configured to be operative to automatically triggergeneration of the layered alert notification related to the battery byautomatically triggering generation of the layered alert notificationrelated to the battery 57002 when at least one of the receivedindividual status information reflects that at least one of thetemperature conditions of the battery exceeds a threshold temperaturevalue for the battery.

In some embodiments, the node processor may be programmaticallyconfigured to be operative to receive the status data by receivingindividual status information from each of the battery sensors as thestatus data over a time period. In this situation, the node processormay also be programmatically configured to be operative to automaticallytrigger generation of the layered alert notification by being furtheroperative to monitor the received individual status information fromeach of the battery sensors over the time period to identify relativechanges in the individual status information over the time period, andautomatically trigger generation of the layered alert notificationrelated to the battery when at least one of the identified relativechanges in the individual status information over the time periodexceeds a time-based relative temperature change threshold for thebattery.

As briefly mentioned above, the system's sensor-based ID node 24120 amay be activated and “wake” from a low power mode based upon the sensordata. For example, the node processor may be programmaticallyconfigured, when executing the battery monitoring program code, to beoperative to automatically activate the sensor-based node (such as IDnode 24120 a shown in FIG. 57) from a low power mode when the receivedstatus data is inconsistent with the battery threshold metric valuemaintained in the sensor-based node memory.

As explained above, the node processor of sensor-based ID node 24120 amay programmatically be configured so as to be operative toautomatically trigger generation of a layered alert notification relatedto the battery 57002 when the received status data is inconsistent withthe battery threshold metric value. The layered alert notificationgenerated may depend on a number for factors. For example, such alayered alert notification may, for example, be generated based upon alevel of inconsistency between the received status data and the batterythreshold metric value, based upon how much the charge status conditiondiffers from the threshold voltage value, based upon how much thetemperature condition of the battery 57002 exceeds the thresholdtemperature value, based upon how much at least one of the temperatureconditions of the battery exceeds the threshold temperature value forthe battery 57002, and/or based upon how many of the battery sensorshave their respective battery status condition exceeding the thresholdtemperature value for the battery.

In another example of system 57000, the layered alert notification mayidentify battery 57002 so that those elements receiving the layeredalert notification will be informed that it is specifically battery57002 having an inconsistent battery status condition relative tothresholds for that battery. In more detail, the node memory storage onsensor-based ID node 24120 a may maintain battery specifier data relatedto the battery 57002 (e.g., exemplary battery specifier data related tobattery 57002 as part of profile data 330 maintained in memory of IDnode 24120 a). As such, the layered alert notification related tobattery 57002 may include an identification of battery 57002 based uponthe battery specifier data (e.g., information on a unique identifier forbattery 57002, information on a characteristic category of battery 57002(such as a lithium-ion type of battery)). Such battery specifier datamay be pre-programmed into the node memory of ID node 24120 a when theID node is associated with the battery 57002 (e.g., during manufacture,during packaging for transport, and the like). This may be accomplishedby having the node processor being further programmatically configuredto be operative to receive the battery specifier data over the wirelesscommunication interface and store the battery specifier data within thenode memory storage.

As noted above, the node processor of ID node 24120 a in system 57000 isoperative to cause the wireless communication interface of ID node 24120a to broadcast the layered alert notification to initiate a mediationresponse related to the battery status condition for battery 57002. Sucha mediation response may be a request for intervention in the transportof battery 57002. For example, as shown in FIG. 59, system 59000 isshown with similar components as system 44000 in FIG. 44, but FIG. 59shows several node-enhanced battery systems (e.g., NEB 1, NEB 2, NEB 3)within shipping container 24300 a. In this example, the sensor-based IDnode as part of NEB1 may cause its wireless communication interface tobroadcast a layered alert notification to initiate a mediation responserelated to the battery status condition for the battery of NEB 1. Such amediation response may be a request for intervention in the transport ofNEB 1 (notably, the battery within NEB 1). As such, the layered alertnotification may be received by command node 24160, which may directexternal transceiver 24150 to display a prompt message requestingintervention (e.g., a change in course of transit vehicle 24200 or aninspection be conducted of NEB 1). In another example, the mediationresponse may be a request for automatic fire suppression interventionfor the battery (e.g., where command node 24160 responds to the layeredalert notification broadcast from the ID node in NEB1, and directs firesuppression system 25010 to dispense fire suppressant material withinshipping container 24300 a to as to intervene in response to thenotification from NEB 1).

FIG. 58 is a diagram illustrating an exemplary node-enabled packagesystem for a battery having integrated environmental detection andreporting functionalities in accordance with an embodiment of theinvention. Referring now to FIG. 58, an exemplary node-enhanced batterypackage system 58000 (NEBP, also referenced as a node-enabled batterypackage system) is shown having a battery package 58002 configured to asa type of housing that packages a battery (e.g., a lithium-ion battery).Such a package 58002 may, in some embodiments, be implemented aspackaging that encloses a battery (such as that shown in FIG. 58) in asealable package that may selectively opened/closed, but package 58002may be implemented as a housing that conformally holds multiple batterycells that make up the battery. In other words, an embodiment of package58002 may be similar to battery 57002 (which has battery cells and ahousing to contain such cells together as a unit) but does not includethe actual battery cells. As such, an embodiment of system 58000 mayhave battery package 58002 along with a sensor-based node 24120 aattached to the package 58002 without having power cells or fuel cellsthat power a battery that may be further inserted into and contained bypackage 58002. As shown in FIG. 58, exemplary package 58002 includes abase 58005, walls 58010, and a lid or top 58003 that collectively definean interior space 58015 within which a battery may be disposed andmonitored as part of system 58000.

Exemplary system 58000 further includes a sensor-based ID node 24120 aattached to the battery package 58002. As shown in FIG. 58, ID node24120 a is mounted on or within package 58002, but furtherimplementations may attach ID node 24120 a in a manner that incorporatesthe ID node 24120 a into the physical structure of the package 58002(e.g., integrates ID node 24120 a as part of package 58002). Similar tothat shown in FIG. 57, exemplary sensor-based ID node 24120 a (e.g., animplementation of ID node 120 a explained above and with reference toFIG. 3) used as part of system 58000 and shown in FIG. 58 includes anode processor, a node memory storage coupled to the node processor, awireless communication interface coupled to the processor, as well asone or more sensors coupled to the processor and disposed on parts ofpackage 58002. The node memory storage maintains at least a batterymonitoring program code and a battery threshold metric value (e.g., aspart of the node control and management code 325 stored on memory 320 ofID node 120 a). The wireless communication interface (e.g., variablepower short range communication interface 375) may be a low powercommunication interface capable of Bluetooth Low Energy formattedcommunications. The sensor(s) deployed as part of sensor-based ID node24120 a is generally operative to sense a battery status condition forthe battery to be held by package 58002. Those skilled in the art willappreciate that such a sensor (e.g., sensor 360) may be integrated anddeployed with ID node 24120 a, but may be remotely disposed (e.g.,sensors 58360 a-58360 j) at different locations on the battery package58002.

As part of system 58000, the processor of sensor-based ID node 24120 ashown in FIG. 58 is programmatically configured, when executing thebattery monitoring program code, to be operative to receive status datafrom the sensor (where the status data reflecting the battery statuscondition as sensed by the sensor); automatically trigger generation ofa layered alert notification related to the battery when the receivedstatus data is inconsistent with the battery threshold metric value; andcause the wireless communication interface to broadcast the layeredalert notification to initiate a mediation response related to thebattery status condition for the battery held by battery package 58002.

In more detail, the battery status condition sensed by the sensor on thesensor-based node may be a charge status condition of the battery heldin package 58002 (e.g., a voltage level indicative of the charge statusof a battery held in package 58002). In more detail, an example may havea sensor on sensor-based ID node 24120 a shown in FIG. 58 that is placedon a location of package 58002 and connected to terminals of the batteryheld in package 58002. As such, the node processor may beprogrammatically configured to be operative to automatically triggergeneration of the layered alert notification (a) when the batterythreshold metric value is a threshold voltage value and (b) when thereceived status data on the charge status condition of the battery heldby package 58002 is less than that threshold voltage value.

In another example, the battery status condition sensed by the sensor onthe sensor-based node on package 58002 may be a temperature condition ofthe battery held in package 58002. As such, the node processor may beprogrammatically configured to be operative to automatically triggergeneration of the layered alert notification (a) when the batterythreshold metric value is a threshold temperature value and (b) when thereceived status data on the temperature condition of the battery held bypackage 58002 exceeds that threshold temperature value.

As noted, exemplary sensor-based ID node 24120 a is shown in FIG. 58 aspart of system 58000 equipped with multiple battery sensors 58360a-58360 j disposed on different points of the battery package 58002. Inthis configuration, an embodiment may have the battery status conditionsensed by each of the battery sensors being temperature conditions ofthe battery held in package 58002, where each of the temperatureconditions corresponds to the respective different point on (or in) thebattery package 58002 where the respective battery sensor is disposed.As such, the node processor on ID node 24120 a of package 58002 may beprogrammatically configured to be operative to receive the status databy receiving individual status information from each of the batterysensors as the status data. Furthermore, the node processor may beprogrammatically configured to be operative to automatically triggergeneration of the layered alert notification related to the batteryhoused by the battery package 58002 by automatically triggeringgeneration of the layered alert notification related to the battery57002 when at least one of the received individual status informationreflects that at least one of the temperature conditions of the batteryhoused by the battery package 58002 exceeds a threshold temperaturevalue for the battery housed by the battery package 58002.

In some embodiments, the node processor may be programmaticallyconfigured to be operative to receive the status data by receivingindividual status information from each of the battery sensors as thestatus data over a time period. In this situation, the node processormay also be programmatically configured to be operative to automaticallytrigger generation of the layered alert notification by being furtheroperative to monitor the received individual status information fromeach of the battery sensors over the time period to identify relativechanges in the individual status information over the time period, andautomatically trigger generation of the layered alert notificationrelated to the battery housed by the battery package 58002 when at leastone of the identified relative changes in the individual statusinformation over the time period exceeds a time-based relativetemperature change threshold for the battery housed by package 58002.

Similar to that described above in system 57000, the sensor-based IDnode 24120 a in system 58000 may be activated and “wake” from a lowpower mode based upon the sensor data. For example, the node processormay be programmatically configured, when executing the batterymonitoring program code, to be operative to automatically activate thesensor-based node (such as ID node 24120 a shown in FIG. 58) from a lowpower mode when the received status data is inconsistent with thebattery threshold metric value maintained in the sensor-based nodememory.

As explained above, the node processor of sensor-based ID node 24120 ain system 58000 may programmatically be configured so as to be operativeto automatically trigger generation of a layered alert notificationrelated to the battery housed by package 58002 when the received statusdata is inconsistent with the battery threshold metric value. Thelayered alert notification generated may depend on a number for factors.For example, such a layered alert notification may, for example, begenerated based upon a level of inconsistency between the receivedstatus data and the battery threshold metric value, based upon how muchthe charge status condition differs from the threshold voltage value,based upon how much the temperature condition of the battery housed bypackage 58002 exceeds the threshold temperature value, based upon howmuch at least one of the temperature conditions of the battery housed bypackage 58002 exceeds the threshold temperature value for that battery,and/or based upon how many of the battery sensors have their respectivebattery status condition exceeding the threshold temperature value forthe battery housed by package 58002.

In another example of system 58000, the layered alert notification mayidentify the battery housed by package 58002 so that those elementsreceiving the layered alert notification will be informed that it isspecifically the battery housed by package 58002 having an inconsistentbattery status condition relative to thresholds for that battery. Inmore detail, the node memory storage on sensor-based ID node 24120 a aspart of system 58000 may maintain battery specifier data related to thebattery housed by package 58002 (e.g., exemplary battery specifier datarelated to the battery housed by package 58002 as part of profile data330 maintained in memory of ID node 24120 a). As such, the layered alertnotification related to the battery housed by package 58002 may includean identification of the battery housed by package 58002 based upon thebattery specifier data (e.g., information on a unique identifier for thebattery housed by package 58002, information on a characteristiccategory of the battery housed by package 58002 (such as a lithium-iontype of battery)). Such battery specifier data may be pre-programmedinto the node memory of ID node 24120 a when the ID node is associatedwith the battery housed by package 58002 (e.g., during manufacture,during packaging for transport, and the like). This may be accomplishedby having the node processor being further programmatically configuredto be operative to receive the battery specifier data over the wirelesscommunication interface and store the battery specifier data within thenode memory storage.

As noted above, the node processor of ID node 24120 a in system 58000 isoperative to cause the wireless communication interface of the package'sID node 24120 a to broadcast the layered alert notification to initiatea mediation response related to the battery status condition for thebattery housed by package 58002. Such a mediation response may be arequest for intervention in the transport of package 58002 (includingthe battery housed by package 58002). For example, as shown in FIG. 59,system 59000 is shown with similar components as system 44000 in FIG.44, but FIG. 59 further shows several node-enhanced battery packagesystems (e.g., NEBP 1, NEBP 2, NEBP 3) within shipping container 24300a. In this example, the sensor-based ID node as part of NEBP 1 may causeits wireless communication interface to broadcast a layered alertnotification to initiate a mediation response related to the batterystatus condition for the battery housed within the package of NEBP 1.Such a mediation response may be a request for intervention in thetransport of NEBP 1 (notably, the battery housed within NEBP 1). Assuch, the layered alert notification may be received by command node24160, which may direct external transceiver 24150 to display a promptmessage requesting intervention (e.g., a change in course of transitvehicle 24200 or an inspection be conducted of NEBP 1). In anotherexample, the mediation response may be a request for automatic firesuppression intervention for the battery housed within the node-enhancedbattery package system (e.g., where command node 24160 responds to thelayered alert notification broadcast from the ID node in NEBP 1, anddirects fire suppression system 25010 to dispense fire suppressantmaterial within shipping container 24300 a to as to intervene inresponse to the notification from NEBP 1).

In a further embodiment, system 58000 may be modified so that multiplesensor-based ID nodes are attached to (or integrated as part of) thebattery package, instead of using a single sensor-based ID node 24160 ain or on package 58002 as shown in FIG. 58. In this further embodiment,each of the multiple sensor based ID nodes is similarly configured asnode 24160 a as explained above with reference to and as shown in FIG.58. As such, the sensor (or sensors) for each of the sensor-based nodesare disposed at differing locations on the battery package, where eachof the sensors is operative to sense a battery status condition for thebattery housed within the battery package.

The node processor in each of this further system embodiment'ssensor-based nodes is programmatically configured, when executing thebattery monitoring program code, to be operative to receive status datafrom that node's sensor (where the status data reflects the batterystatus condition as sensed by that particular sensor); automaticallytrigger generation of a layered alert notification related to thebattery housed within the package when the received status data isinconsistent with the battery threshold metric value; and cause thewireless communication interface to broadcast the layered alertnotification to initiate a mediation response related to the batterystatus condition for the battery housed within this system's batterypackage.

In more detail, the further system embodiment may have the sensor forone of the sensor-based nodes be coupled to the terminals of the batteryhoused within the battery package so that the sensor data reflects acharge status condition of the battery. As such, the node processor ofthat sensor-based node may be programmatically configured to beoperative to automatically trigger generation of the layered alertnotification when the battery threshold metric value comprises athreshold voltage value and when the received status data on the chargestatus condition of the battery housed within the package is less thanthe threshold voltage value.

The battery status condition sensed by the sensor on the sensor-basednodes may, in other examples, be a temperature condition relative to thelocation on the battery package associated with the respective sensor onthe particular one of the sensor-based nodes. As such, the nodeprocessor of each of the sensor-based nodes may be programmaticallyconfigured to be operative to automatically trigger generation of thelayered alert notification when the battery threshold metric valuecomprises a threshold temperature value and when the received statusdata on the temperature condition relative to the location on thebattery package associated with the respective sensor on thesensor-based nodes exceeds the threshold temperature value.

Similar to the embodiments described above relative to system 58000,this further embodiment may have the node processor operative to receivethe status data over a time period. In such a situation, the nodeprocessor of each of the sensor-based nodes may be programmaticallyconfigured to be operative to automatically trigger generation of thelayered alert notification by being further operative to monitor thereceived status data over the time period to identify relative changesin the received status over the time period, and automatically triggergeneration of the layered alert notification related to the batteryhoused within the package when at least one of the identified relativechanges in the received status data over the time period exceeds atime-based relative temperature change threshold for the battery housedwithin the package.

In more detail, the node processor of each of the sensor-based nodes inthis further embodiment may be programmatically configured, whenexecuting the battery monitoring program code, to be operative toautomatically activate the respective sensor-based node from a low powermode when the received status data is inconsistent with the batterythreshold metric value.

The layered alert notification generated by the node processor in eachof the sensor-based nodes in this further embodiment may be based upon avariety of factors. For example, it may be based upon a level ofinconsistency between the received status data and the battery thresholdmetric value; based upon how much the charge status condition differsfrom the threshold voltage value; and/or based upon how much thetemperature condition of the battery housed within the system's batterypackage exceeds the threshold temperature value.

Similar to the embodiments described above, the mediation response mayinvolve a request for intervention in transport of the battery housedwithin the package or a request for automatic fire suppressionintervention for the battery housed by the battery package.

Additionally, this further system embodiment may have the node memorystorage on each of the sensor-based nodes maintaining battery specifierdata related to the battery housed with the package as described above(e.g., exemplary battery specifier data related to a battery housedwithin package 58002 as part of profile data 330 maintained in memory ofID node 24120 a and other ID nodes disposed on package 58002). As such,the layered alert notification related to the battery housed within thepackage in this system embodiment may include an identification of thatbattery based upon the battery specifier data (e.g., information on aunique identifier for the battery, information on a characteristiccategory of the battery (such as a lithium-ion type of battery)). Suchbattery specifier data may be pre-programmed into the node memory ofeach sensor-based node on the package when the battery to be housedwithin the battery package is assembled with the package (e.g., duringmanufacture, during packaging for transport, and the like). This may beaccomplished by having the node processor for each sensor-based nodebeing further programmatically configured to be operative to receive thebattery specifier data over the wireless communication interface andstore the battery specifier data within the node memory storage.

Another embodiment of an alternative type of node-enhanced (ornode-enabled) battery package is configured to house multiple batterieswhere each is monitored by a sensor-based node (e.g., sensor-basedwireless ID node 24160 a). This additional embodiment extends thebattery package generally to have different battery storage locationswithin the package and where specific sensor-based nodes are deployed onor as part of the package to individually monitor batteries housedwithin each of the different battery storage locations within thepackage. FIG. 60A is a diagram illustrating an exemplarymulti-node-enabled package system for transporting multiple batterieshaving integrated environmental detection and reporting functionalitiesin accordance with an embodiment of the invention. Referring now to FIG.60A, an exemplary multi-node-enhanced multi-battery package system 60000(NEMBP, also referenced as a node-enabled multi-battery package system)is shown having a battery package 60002 configured to as a type ofhousing that packages multiple batteries (e.g., different batteries thatmay include one or more lithium-ion batteries). Such a package 60002may, in some embodiments, be implemented as packaging that encloses thebatteries (such as that shown in FIG. 60A) in a sealable package thatmay be selectively opened/closed, but package 60002 may be implementedas a housing that conformally holds multiple batteries in differentbattery storage locations 60015 a-60015 c defined within package 60002.In other words, an embodiment of package 60002 may provide batterystorage locations 60015 a-60015 c but does not include the actualbatteries that will be disposed within them (a further embodiment mayinclude the batteries as part of system 60000).

As shown in FIG. 60A, exemplary package 60002 includes a base 60005 thatsupports the batteries to be housed within package 60002; and anenclosing structure coupled to base 60005 having, for example, walls60010 and a lid or top 60003. The enclosing structure (e.g., walls 60010and lid 60003) and the base 60005 collectively define an interiorstorage space within the battery package 60002 for maintaining thebatteries. In particular and as shown in FIG. 60A, package 60002 includefurther interspersed separators 60020 a, 60020 b that divide theinterior storage space and define the different battery storagelocations 60015 a-60015 c within the interior storage space wheredifferent batteries may be housed and be monitored by differentsensor-based ID nodes 60120 a-60120 c disposed in a respective one oflocations 60015 a-60015 c.

As shown in FIG. 60A, ID nodes 24120 a-24120 c are each mounted on orwithin package 60002 in respectively different battery storage locations60015 a-60015 c, but further implementations may attach each of ID nodes24120 a-24120 c in a manner that incorporates the particular ID nodeinto the physical structure of the package 60002 (e.g., integrates IDnode as part of package 60002). Similar to that shown in FIGS. 57 and58, each of exemplary sensor-based ID nodes 24120 a-24120 c (e.g., animplementation of ID node 120 a explained above and with reference toFIG. 3) used as part of system 60000 and shown in FIG. 60A includes anode processor, a node memory storage coupled to the node processor, awireless communication interface coupled to the processor, as well asone or more sensors coupled to the processor and disposed on parts ofpackage 60002. The node memory storage maintains at least a batterymonitoring program code and a battery threshold metric value (e.g., aspart of the node control and management code 325 stored on memory 320 ofID node 120 a). The wireless communication interface (e.g., variablepower short range communication interface 375) may be a low powercommunication interface capable of Bluetooth Low Energy formattedcommunications. The sensor(s) deployed as part of each of sensor-basedID nodes 24120 a-24120 c is generally operative to sense a batterystatus condition for the battery held by package 60002 in the particularone of the battery locations 60015 a-60015 c associated with theparticular sensor-based ID node having that sensor(s). Those skilled inthe art will appreciate that such a sensor (e.g., sensor 360) may beintegrated and deployed with its respective ID node, but may be remotelydisposed (e.g., sensors 60360 a 1-60360 c 3) at different locationswithin the different battery storage locations 60015 a-60015 c of thebattery package 60002. For example, within battery storage location60015 a, sensor-based ID node 24120 a is coupled to each of sensors60360 a 1-60360 a 3. In like manner, within battery storage location60015 b, sensor-based ID node 24120 b is coupled to each of sensors60360 b 1-60360 b 3. Similarly, within battery storage location 60015 c,sensor-based ID node 24120 c is coupled to each of sensors 60360 c1-60360 c 3. In this way, package 60002 offers different storagelocations 60015 a-60015 c for different batteries that will be monitoredby their own sensor-based node capable as part of system 60000.

FIG. 61 is a diagram illustrating an exemplary improved system forcoordinated mediation action in response to an identified environmentalanomaly related to the shipping container transporting an exemplarynode-enabled battery system, an exemplary node-enabled package systemfor a battery, and an exemplary multi-node-enabled package system fortransporting multiple batteries in accordance with an embodiment of theinvention. Referring now to FIG. 61, system 61000 is shown with similarcomponents as system 59000 shown in FIG. 59. In particular, as itrelates to the NEB and NEBP systems shown in FIG. 61, functionality ofsystem 61000 that has exemplary command node 24160 (a type of masternode) interacting with the NEB and NEBP systems shown and operating ashas been described above relative to FIG. 59. However, exemplary system61000 illustrates an exemplary multi-node-enabled package system (i.e.,NEMBP 1) that may be implemented as exemplary system 6000 and alsointeract with command node 24160. In more detail, the wirelesscommunication interface coupled to the node processor on each of thesensor-based ID nodes 24120 a-24120 c disposed in package 60002 ofsystem 60000 (e.g., NEMBP 1 shown in FIG. 61) is configured towirelessly communicate with the command node 24160.

As shown in system 61000, the node processor in each of the ID nodesdeployed in NEMBP 1 is programmatically configured, when executing thebattery monitoring program code, to be operative to receive status datafrom the sensor of the respective ID node (where the status datareflects the battery status condition for the particular batterydisposed in the one of the battery storage locations 60015 a-60015 cassociated with the respective ID node on NEMBP 1). The node processorin each of the ID nodes deployed in NEMBP 1 is further programmaticallyconfigured to be operative to, when the received status data from aparticular ID node is inconsistent with the battery threshold metricvalue, automatically trigger generation of a layered alert notificationrelated to the respective battery disposed in that ID node's batterystorage location; and then cause the wireless communication interface ofthat the ID node to broadcast the layered alert notification to thecommand node 24160.

A further embodiment of NEMBP 1 (e.g., system 60000) as shown in FIG.60B includes an exemplary master node 60110 attached to battery package60002 separate from each of the ID nodes 24120 a-24120 c. Exemplarymaster node 60110 is disposed on or within package 60002, is affixed ina temporary or removable manner, and is operative to communicate with anexternal node, such as command node 24160 or in some instances directlywith external transceiver 24150 or onboard fire suppression system25010. The exemplary master node 60110, as an additional management nodecomponent attached to and associated with multiple battery package 60002(NEMBP 1), is configured to receive the layered alert notification fromany of the ID nodes 24120 a-24120 c; responsively identify anenvironmental anomaly for a particular one of the batteries housedwithin NEMBP 1 based upon the layered alert notification and anidentification of which of the ID nodes 24120 a-24120 c transmitted thelayered alert notification; and transmit a package level alertnotification to the external node (e.g., the command node 24160 disposedwithin shipping container 24300 a, external transceiver 24150, and/orfire suppression system 25010) to initiate a mediation response relatedto the battery status condition for the batteries in NEMBP 1 (i.e., atleast one of those batteries) where the package level alert notificationidentifies the environmental anomaly for the batteries.

In more detail, exemplary system 61000 may have the sensor for one ofthe sensor-based ID nodes in NEMBP 1 be coupled to terminals of theparticular battery disposed in the particular battery storage locationassociated with that ID node so that the sensor data reflects a chargestatus condition of that particular one of the batteries housed withinNEMBP 1. As such, the node processor of that sensor-based node may beprogrammatically configured to be operative to automatically triggergeneration of the layered alert notification when the battery thresholdmetric value comprises a threshold voltage value and when the receivedstatus data on the charge status condition of the battery housed withinthat location of the package is less than the threshold voltage value.

The battery status condition sensed by the sensor on the sensor-basednodes may, in other examples, be a temperature condition relative to thelocation on the battery package (e.g., a temperature conditionassociated with the one of the batteries disposed in one of the batterystorage locations 60015 a-60015 c). As such, the node processor of eachof the sensor-based ID nodes may be programmatically configured to beoperative to automatically trigger generation of the layered alertnotification when the battery threshold metric value comprises athreshold temperature value and when the received status data on thetemperature condition relative to the location on the battery packageassociated with the respective sensor on the sensor-based ID nodesexceeds the threshold temperature value.

Similar to the embodiments described above relative to system 58000,system 61000 (using components of NEMBP 1) may have the node processorof each of the ID nodes operative to receive the status data over a timeperiod. In such a situation, the node processor of each of thesensor-based ID nodes may be programmatically configured to be operativeto automatically trigger generation of the layered alert notification bybeing further operative to monitor the received status data over thetime period to identify relative changes in the received status over thetime period, and automatically trigger generation of the layered alertnotification related to the particular battery housed within the batterystorage location associated with that ID node when at least one of theidentified relative changes in the received status data over the timeperiod exceeds a time-based relative temperature change threshold forthat battery.

In more detail, the node processor of each of the sensor-based nodes inthis embodiment may be programmatically configured, when executing thebattery monitoring program code, to be operative to automaticallyactivate the respective sensor-based ID node from a low power mode whenthe received status data is inconsistent with the battery thresholdmetric value.

The layered alert notification generated by the node processor in eachof the sensor-based ID nodes in NEMBP 1 as part of system 61000 may bebased upon a variety of factors. For example, it may be based upon alevel of inconsistency between the received status data and the batterythreshold metric value; based upon how much the charge status conditiondiffers from the threshold voltage value; and/or based upon how much thetemperature condition of the particular one of the batteries housedwithin the system's battery package 60002 exceeds the thresholdtemperature value.

Similar to the embodiments described above, the mediation response aspart of system 61000 may involve a request for intervention in transportof the particular one of the batteries housed within the package 60002of NEMBP 1 or a request for automatic fire suppression intervention forthe particular one of the batteries housed within the package 60002 ofNEMBP 1.

Additionally, exemplary system 61000 may have the node memory storage oneach of the sensor-based ID nodes in NEMBP 1 maintaining batteryspecifier data related to the particular battery located in the storagelocation of that ID node as described above (e.g., exemplary batteryspecifier data related to a battery housed within one of the locations60015 a-60015 c of package 60002 as part of profile data 330 maintainedin memory of ID node 24120 a and other ID nodes disposed on package60002). As such, the layered alert notification may include anidentification of that battery based upon the battery specifier data(e.g., information on a unique identifier for the battery, informationon a characteristic category of the battery (such as a lithium-ion typeof battery)). Such battery specifier data may be pre-programmed into thenode memory of each sensor-based ID node in NEMBP 1 when the differentbatteries to be housed within the battery package 60002 are placed orassembled with the package (e.g., during manufacture, during packagingfor transport, and the like). This may be accomplished by having thenode processor for each sensor-based ID node in NEMBP 1 being furtherprogrammatically configured to be operative to receive the batteryspecifier data over the wireless communication interface and store thebattery specifier data within its own node memory storage.

In still a further embodiment of system 61000 that uses NEMBP 1, thepackage level alert notification transmitted by the package's masternode adaptively identifies the mediation response depending upon theidentification of which of the ID nodes in NEMBP 1 transmitted thelayered alert notification. Expanding on this further, an embodiment mayhave the node memory storage on each of the ID nodes in NEMBP 1 furthermaintaining usage context data (e.g., part of profile data 330) relatedto the particular battery that is disposed in the battery storagelocation associated with the respective one of the ID nodes. As such,the package level alert notification transmitted by the master node mayadaptively identify the mediation response depending upon (a) theidentification of which of the ID nodes transmitted the layered alertnotification, and (b) based upon the usage context data and/orcharacteristic category (e.g., type) related the one of the batteriesdisposed in the one of the battery storage locations associated with therespective one of the ID nodes transmitting the layered alertnotification.

In one embodiment, such usage context data may indicate an active usagestatus of the battery in NEMBP 1. Examples of such an active usagestatus may be a present battery charging state (e.g., a standby state, acharging state, and a discharging state) or a current battery healthstate (e.g., charge cycle count, delivered voltage, internal resistance,current charge capacity, and the like). In some embodiments, the ID nodesensor disposed with a battery within NEMBP1 may be a power sensor(e.g., a type of sensor 360 connected to a battery, such as sensor 57360a connected to terminals 57005 and 57010 of battery 57002 shown in FIG.57). Such a power sensor is operative to detect the active usage statusof the battery. In this situation, the advertising signals broadcast bythe that ID node may include usage context data indicating the activeusage status as detected by the power sensor and, in some embodiments,may allow command node 24160 to identify or update the usage contextdata when wirelessly monitoring the advertising signals.

In another embodiment, the usage context data may indicate a location ofthe battery pack used in NEMBP 1. For example, the usage context datamay include information on the battery pack's proximity to otherimportant items (e.g., mission critical or sensitive electronics thatmay be damaged by smoke or heat) or dangerous/hazardous materials withincontainer 24300 a or situated near the location of NEMBP 1 as disposedwithin container 24300 a (e.g., materials that may catch fire and causea larger explosion). The usage context data may indicate a risk factorassociated with the location of the NEMBP 1 battery—e.g., information onwhether the battery pack is within a specific distance from fuel used bythe transit vehicle 24200 so that an anomaly with the battery pack maycause a larger issue with such fuel (such as flames that may cause alarger explosion). As such, consideration of usage context data of thesetypes allow command node 24160 to dynamically adjust the type ofmediation response to automatically and quickly initiate the appropriatemediation response.

Layered Initiation of Mediated Environmental Anomaly Response UsingNode-Enhanced Battery and Multi-Mode Triggering

The embodiments above describe an exemplary node-enhanced ornode-enabled battery as an apparatus (e.g., NEB1 explained as exemplarynode-enhanced battery (NEB) 57000) or system of elements or a componentof a larger system. However, further embodiments described below maydeploy such an exemplary node-enhanced or node-enabled battery as partof different systems for layered initiation of a mediation response to abattery-related environmental anomaly. In general, when a node-enabledbattery device suddenly ceases to broadcast where contextually it shouldstill be broadcasting (e.g., detected based on a change in broadcastedadvertising messages expected to be broadcast from the particularwireless node disposed with the device), an initially small temperaturerise detected by a secondary device near the node-enabled battery device(or within the same shipping container as the device) may indicate anenvironmental anomaly issue. From a system perspective, that change maybe detected by a managing device—e.g., a command node or masternode—that is also in contact with the secondary device (who sends sensordata indicating the small temperature rise to the managing device). Insuch embodiments, the managing device interacts with both thenode-enhanced battery device as well as a nearby secondary sensor-baseddevice in making a determination that there may be an environmentalanomaly.

More specifically, the managing device may receive and use bothsensor-based information (e.g., the environmental sensor data, such astemperature data) as well as non-environmental detected information(e.g., the existence or absence of expected advertising signals) inmaking this determination of whether there is a potential environmentalanomaly. Such multi-mode detection embodiments may be particularlyhelpful when a fire spreads rapidly, the broadcasting devices may bedisappearing so quickly that relying solely upon changing values ofenvironmental sensor data may not provide enough reaction time and maylead to catastrophic damage (e.g., loss of a shipping container beforethe container command node may sense a sufficient an increase intemperature to warrant transmitting an alert notification to initiate amediation response). The use of multi-mode detection embodiments thatmonitor for an environmental anomaly may generally involve a firsttriage level, and then get further data to verify or get higher qualitydata (issue command or request supporting information from other networkdevices) as a second triage level before initiating the mediationresponse.

The term “mediation” is used as a broad term which may includeactivating an automate fire suppression system, initiate manual firesuppression, informing the pilot or operator of a transit vehicle toprepare for landing, signaling a remote system to prepare foremergency/initiate rescue, and the like. Exemplary mediation responsesmay also include informing customers their packages are lost and toinitiate replacement as a mode to handle critical inventory orjust-in-time operations who will be impacted by diverted vehicles (e.g.,aircraft), packages damaged by fire suppression (or other mediation), orcritical loss of items.

FIG. 62 is a diagram illustrating an exemplary system for layeredinitiation of a mediation response to a battery-related environmentalanomaly involving a node-enabled battery apparatus, at least onesecondary sensor-based ID node, and a command node in accordance with anembodiment of the invention. Referring now to FIG. 62, exemplary system62000 illustrates an exemplary system for layered initiation of amediation response to a battery-related environmental anomaly and isshown with similar components as shown in system 59000 of FIG. 59, butis simplified to show an exemplary node-enhanced battery system, NEB 1(also referenced as a node-enabled battery apparatus), wirelesssensor-based ID nodes 1-3, and exemplary command node 24160 disposedwithin shipping container 24300 a. Consistent with the prior descriptionof an exemplary node-enabled battery (as a system or apparatus ofdistinct parts), NEB 1 in system 62000 generally includes at least onebattery (e.g., battery 57002), and a wireless node (e.g., ID node 24120a shown in FIG. 57 to be part of the node-enhanced battery system 57000)disposed with the battery (e.g., attached to the battery or integratedwith the battery itself).

The wireless node component of NEB 1 has a wireless communicationinterface operative to broadcast a plurality of advertising signals overtime. Wireless sensor-based ID nodes 1-3 are shown in FIG. 62 asdifferent secondary sensor-based nodes where each has an environmentalsensor and a wireless communication interface operative to broadcastenvironmental sensor data generated by the environmental sensor. Forexample, ID node 1 shown in FIG. 62 is disposed next to or proximate NEB1 (e.g., ID node 1 is next to with no intervening batteries, shipments,packages, or other objects between the node-enabled battery apparatus(NEB 1) and ID node 1). Command node 24160 of system 62000 is inwireless communication with NEB 1 and each of the secondary sensor-basednodes (e.g., ID nodes 1-3).

As part of system 62000, command node 24160 is programmaticallyconfigured (via program code, such as part of command node managementand control code 26425 when executing on the processor 26400 of commandnode 24160) to be operative to conduct multiple levels ofbattery-related anomaly monitoring. In particular, command node 24160 isadvantageously operative to conduct an initial level of battery-relatedanomaly monitoring by wirelessly monitoring the advertising signalsbroadcast by NEB 1 for an unanticipated state of ceased broadcasting ofNEB 1 according to a communication profile maintained on the commandnode (e.g., a communication profile for NEB1 as reflected in part ofprofile data 430 stored on command node 24160); and wirelesslymonitoring the broadcasted environmental sensor data from a secondarysensor-based node (e.g., ID node 1). Command node 24160 is furtherprogrammatically operative to identify an initial level of thebattery-related environmental anomaly based on the initial level ofbattery-related monitoring when both the unanticipated state of ceasedbroadcasting is detected and the monitored broadcasted environmentalsensor data reflects at least a first threshold difference change in theenvironmental sensor data; conduct a secondary level of battery-relatedanomaly monitoring of broadcasts from the secondary sensor-based node(e.g., ID node 1) in response to the identified initial level of thebattery-related environmental anomaly; and initiate the mediationresponse to the battery-related environmental anomaly based upon thesecondary level of battery-related anomaly monitoring by broadcasting alayered alert notification.

Command node 24160, as part of system 62000, may be further configuredto be operative to conduct the secondary level of battery-relatedanomaly monitoring by wirelessly monitoring the advertising signalsbroadcast by NEB 1 for an additional unanticipated state of ceasedbroadcasting according to the communication profile maintained oncommand node 24160 for the wireless node in NEB 1, and wirelesslymonitoring for additional environmental sensor data from ID node 1 (asthe secondary sensor-based node) to verify the initial level of thebattery-related environmental anomaly.

In some embodiments of system 62000, the reporting rate from thesecondary sensor-based node may be changed as a refinement. For example,command node 24160 may be further programmatically configured to beoperative to conduct the secondary level of battery-related anomalymonitoring by instructing ID node 1 (as the secondary sensor-based node)to broadcast the environmental sensor data at a second messaging ratethat exceeds an initial messaging rate (e.g., a rate of broadcasting setas an initial value correlated to an environmental risk associated withthe battery 57002 of NEB 1). The second messaging rate for ID node 1 (asthe secondary sensor-based node) may be a predetermined higher messagingrate based upon a type of material existing within battery 57002 of NEB1. Once instructing ID node 1 to use the second messaging rate, thecommand node may initiate the mediation response to the battery-relatedenvironmental anomaly in response to the secondary level ofbattery-related anomaly monitoring by broadcasting the layered alertnotification when both another unanticipated state of ceasedbroadcasting is detected and the broadcasted environmental sensor databroadcast at the second messaging rate reflects at least the firstthreshold difference change in the environmental sensor data.

In a further embodiment of system 62000, command node 24160 may befurther programmatically configured to be operative to conduct thesecondary level of battery-related anomaly monitoring by being operativeto (a) wirelessly monitor the advertising signals broadcast by NEB 1 foran additional unanticipated state of ceased broadcasting according tothe communication profile maintained on command node 24160 for thewireless node of NEB 1; (b) wirelessly monitor for additionalenvironmental sensor data from ID node 1 (as the secondary sensor-basednode) to verify the initial level of the battery-related environmentalanomaly; and (c) identify the secondary level of battery-related anomalywhen both another unanticipated state of ceased broadcasting is detectedand the broadcasted environmental sensor data reflects at least a secondthreshold difference change in the environmental sensor data (where thesecond threshold difference change is greater than the first thresholddifference change).

In additional embodiments of system 62000, command node 24160 mayinitiate different types of mediation responses. For example, thebroadcasted layered alert notification from command node 24160 may causeactivation of an automatic fire suppression system (e.g., exemplaryonboard fire suppression system 25010) targeting the container 24300 ahaving the battery of NEB 1. In another example, the broadcasted layeredalert notification from command node 24160 may be a message requestingmanual fire suppression of the battery (e.g., a message that directs adisplay on external transceiver 24150 to display a prompted message thatrequests manual fire suppression for the battery in NEB 1). In a furtherexample, the broadcasted layered alert notification from command node24160 may be a message requesting preparations to cease transportationof the battery in NEB 1 (e.g., a message providing guidance to apreferred location, such as where the transit route started, a close byintermediate destination, and the like). In still another example, thebroadcasted layered alert notification from command node 24160 may be amessage to inform an entity associated with the battery in NEB 1 (e.g.,a battery supplier, shipping client for that battery, a recipient thatis to receive the battery after transport, and the like) that thebattery needs replacement.

As shown in FIG. 62, an embodiment of system 62000 may include more thanone container deployed sensor-based nodes (such as ID nodes 2-3 inaddition to ID node 1 considered as the secondary sensor-based node). Assuch, command node 24160 may be further programmatically operative toconduct the initial level of battery-related anomaly monitoring bywirelessly monitoring the advertising signals broadcast by thenode-enabled battery apparatus, NEB 1, for the unanticipated state ofceased broadcasting according to the communication profile maintained onthe command node for the node-enabled battery apparatus; and wirelesslymonitoring the broadcasted environmental sensor data from each of thecontainer deployed sensor-based nodes, ID nodes 1-3. In this furtherexample, command node 24160 may identify the initial level of thebattery-related environmental anomaly based on the initial level ofbattery-related monitoring when both (a) the unanticipated state ofceased broadcasting is detected and (b) the monitored broadcastedenvironmental sensor data from at least one of ID nodes 1-3 deployed inshipping container 24300 a reflects at least a first thresholddifference change in the environmental sensor data received from the atleast one of ID nodes 1-3.

As part of NEB 1 used in system 62000, the wireless node disposed withthe battery in NEB 1 may maintain battery specifier data related to theparticular battery used in NEB 1 (e.g., battery 57002). Exemplarybattery specifier data related to the battery with the wireless node ofNEB 1 may be maintained, for example, as part of profile data 330maintained in memory of ID node 24120 a shown as part of NEB 1 (alsoexplained as node-enhanced battery system 57000). As such, the layeredalert notification related to the battery in NEB 1 may include anidentification of that battery based upon the battery specifier data(e.g., information on a unique identifier for the battery, informationon a characteristic category of the battery (such as a lithium-ion typeof battery)). Such battery specifier data may be pre-programmed into thenode memory of the wireless node of NEB 1 when the wireless node isassociated with the battery of NEB 1 (e.g., during manufacture, duringpackaging for transport, and the like).

Embodiments of system 62000 may have the mediation response dependingupon usage context data maintained relative to the battery in NEB 1 aswell. For example, as part of exemplary system 62000 shown in FIG. 62,command node 24160 may be further programmatically configured to beoperative to identify the mediation response based upon the secondarylevel of battery-related anomaly monitoring as well as upon usagecontext data related to the battery in NEB 1. In one embodiment, suchusage context data may indicate an active usage status of the battery inNEB 1. Examples of such an active usage status may be a present batterycharging state (e.g., a standby state, a charging state, and adischarging state) or a current battery health state (e.g., charge cyclecount, delivered voltage, internal resistance, current charge capacity,and the like).

In some embodiments, the wireless node disposed with the battery in NEB1 may be deployed with a power sensor (e.g., a type of sensor 360connected to a battery, such as sensor 57360 a connected to terminals57005 and 57010 of battery 57002 shown in FIG. 57). Such a power sensoris operative to detect the active usage status of the battery in NEB 1.In this situation, the advertising signals broadcast by the wirelessnode in NEB 1 may include usage context data indicating the active usagestatus as detected by the power sensor and, in some embodiments, mayallow command node 24160 to identify or update the usage context datawhen wirelessly monitoring the advertising signals.

In another embodiment, the usage context data may indicate a location ofthe battery used in NEB 1. For example, the usage context data mayinclude information on the battery's proximity to other important items(e.g., mission critical or sensitive electronics that may be damaged bysmoke or heat) or dangerous/hazardous materials within container 24300 aor situated near the location of NEB 1 as disposed within container24300 a (e.g., materials that may catch fire and cause a largerexplosion). The usage context data may indicate a risk factor associatedwith the location of the NEB 1 battery—e.g., information on whether thebattery in NEB 1 is within a specific distance from fuel used by thetransit vehicle 24200 so that an anomaly with the NEB 1 battery maycause a larger issue with such fuel (such as flames that may cause alarger explosion). As such, consideration of usage context data of thesetypes allow command node 24160 to dynamically adjust the type ofmediation response to automatically and quickly initiate the appropriatemediation response.

Similar to system 62000, further embodiments may monitor multiplenode-enabled or enhanced batteries as part of a system that initiates amediation response to a battery-related environmental anomaly. FIG. 63is a diagram illustrating an exemplary system for layered initiation ofa mediation response to a battery-related environmental anomalyinvolving multiple node-enabled battery apparatus, at least onesecondary sensor-based ID node, and a command node in accordance with anembodiment of the invention. Referring now to FIG. 63, exemplary system63000 is similar to that shown and explained above relative to system62000 of FIG. 62, but system 63000 includes both NEB 1 and NEB 2 asshown in FIG. 63 and disposed within shipping container 24300 a alongwith sensor-based ID nodes 1-3. As such, an embodiment of system 63000includes wireless nodes, where each of the wireless nodes is disposedwith one of a subset of batteries that may be in shipping container24300 a. For example, exemplary shipping container 24300 a may betransporting a large number of batteries, but a subset of such batteriesmay include the batteries that are part of NEB 1 and NEB 2. Each of NEB1 and NEB 2 include wireless nodes (e.g., ID nodes) that a wirelesscommunication interface that broadcast advertising signals over time.The wireless node disposed with the battery in each of NEB 1 and NEB 2may be attached to or integrated as part of the respective battery. Aspart of exemplary system 63000, sensor based ID node 1 is disposedwithin shipping container 24300 a as shown in FIG. 63. As explainedbefore, ID node 1, as a secondary sensor-based node, has anenvironmental sensor (e.g., sensor 360) and a wireless communicationinterface (e.g., interface 375) operative to broadcast environmentalsensor data generated by the environmental sensor. The command node ofsystem 63000 (command node 24160 as shown in FIG. 63) is attached to thecontainer and is in wireless communication with each of the wirelessnodes in NEB 1 and NEB 2, as well as with ID node 1 (the secondarysensor-based node).

As part of system 63000, command node 24160 is programmaticallyconfigured (via program code, such as part of command node managementand control code 26425 when executing on the processor 26400 of commandnode 24160) to be operative to conduct multiple levels ofbattery-related anomaly monitoring involving multiple wireless nodes aswell as the secondary sensor-based node. In particular, command node24160 is advantageously operative to conduct an initial level ofbattery-related anomaly monitoring by being operative to wirelesslymonitor the advertising signals broadcast by each of the wireless nodesin NEB 1 and NEB 2 for an unanticipated state of ceased broadcasting forat least these wireless nodes according to a communication profilemaintained on command node for each of the wireless nodes in NEB 1 andNEB 2, and wirelessly monitor the broadcasted environmental sensor datafrom the secondary sensor-based node (e.g., ID node 1). Command node24160 is further programmatically operative to identify an initial levelof the battery-related environmental anomaly based on the initial levelof battery-related monitoring when both the unanticipated state ofceased broadcasting is detected and the monitored broadcastedenvironmental sensor data reflects at least a first threshold differencechange in the environmental sensor data. Command node 24160 is furtherprogrammatically operative to conduct a secondary level ofbattery-related anomaly monitoring of broadcasts from ID node 1 (as thesecondary sensor-based node) in response to the identified initial levelof the battery-related environmental anomaly, and initiate the mediationresponse to the battery-related environmental anomaly based upon thesecondary level of battery-related anomaly monitoring by broadcasting alayered alert notification.

Command node 24160, as part of system 63000, may be further configuredto be operative to conduct the secondary level of battery-relatedanomaly monitoring by wirelessly monitoring the advertising signalsbroadcast by the wireless nodes in NEB 1 and NEB 2 for an additionalunanticipated state of ceased broadcasting according to thecommunication profile maintained on command node 24160 for the wirelessnodes in NEB 1 and NEB 2, and wirelessly monitoring for additionalenvironmental sensor data from ID node 1 (as the secondary sensor-basednode) to verify the initial level of the battery-related environmentalanomaly.

As with system 62000, some embodiments of system 63000 may have thereporting rate from ID node 1 (as the secondary sensor-based node) beingchanged as a refinement. For example, command node 24160 may be furtherprogrammatically configured to be operative to conduct the secondarylevel of battery-related anomaly monitoring by instructing ID node 1 (asthe secondary sensor-based node) to broadcast the environmental sensordata at a second messaging rate that exceeds an initial messaging rate(e.g., a rate of broadcasting set as an initial value correlated to anenvironmental risk associated with the battery in NEB 1 or the batteryin NEB 2). The second messaging rate for ID node 1 (as the secondarysensor-based node) may be a predetermined higher messaging rate basedupon a type of material existing within the battery of NEB 1 or NEB 2.Once instructing ID node 1 to use the second messaging rate, the commandnode may initiate the mediation response to the battery-relatedenvironmental anomaly in response to the secondary level ofbattery-related anomaly monitoring by broadcasting the layered alertnotification when both another unanticipated state of ceasedbroadcasting is detected and the broadcasted environmental sensor databroadcast at the second messaging rate reflects at least the firstthreshold difference change in the environmental sensor data.

In a further embodiment of system 63000, command node 24160 may befurther programmatically configured to be operative to conduct thesecondary level of battery-related anomaly monitoring by being operativeto (a) wirelessly monitor the advertising signals broadcast by thewireless nodes in NEB 1 and NEB 2 for an additional unanticipated stateof ceased broadcasting according to the communication profile maintainedon command node 24160; (b) wirelessly monitoring for additionalenvironmental sensor data from ID node 1 (as the secondary sensor-basednode) to verify the initial level of the battery-related environmentalanomaly; and (c) identify the secondary level of battery-related anomalywhen both another unanticipated state of ceased broadcasting is detectedand the broadcasted environmental sensor data reflects at least a secondthreshold difference change in the environmental sensor data (where thesecond threshold difference change is greater than the first thresholddifference change).

In additional embodiments of system 63000, command node 24160 mayinitiate different types of mediation responses. For example, thebroadcasted layered alert notification from command node 24160 may causeactivation of an automatic fire suppression system (e.g., exemplaryonboard fire suppression system 25010) targeting the container 24300 ahaving the battery of NEB 1 and NEB 2. In another example, thebroadcasted layered alert notification from command node 24160 may be amessage requesting manual fire suppression of one of the batteries inNEB 1 or NEB 2 (e.g., a message that directs a display on externaltransceiver 24150 to display a prompted message that requests manualfire suppression for the battery in NEB 1 or NEB 2). In a furtherexample, the broadcasted layered alert notification from command node24160 may be a message requesting preparations to cease transportationof the battery in NEB 1 or NEB 2 (e.g., a message providing guidance toa preferred location, such as where the transit route started, a closeby intermediate destination, and the like). In still another example,the broadcasted layered alert notification from command node 24160 maybe a message to inform an entity associated with the battery in NEB 1 orNEB 2 (e.g., a battery supplier, shipping client for that battery, arecipient that is to receive the battery after transport, and the like)that the battery needs replacement.

As part of NEB 1 or NEB 2 used in system 63000, the wireless nodedisposed with the battery in NEB 1 and the wireless node disposed withthe battery in NEB 2 may each maintain battery specifier data related tothe respective associated battery used in NEB 1 or NEB 2. Exemplarybattery specifier data related to the particular battery may bemaintained, for example, as part of profile data 330 maintained inmemory of the wireless node shown as part of NEB 1 and NEB 2. As such,the layered alert notification related to the battery in NEB 1 or NEB 2may include an identification of the particular battery in NEB 1 or NEB2 based upon the battery specifier data. Such battery specifier data maybe pre-programmed into the node memory of the wireless nodes of NEB 1and NEB 2 when the respective wireless node is associated with therespectively associated battery (e.g., during manufacture, duringpackaging for transport, and the like).

Similar to embodiments of system 62000, embodiments of system 63000 mayhave the mediation response depending upon usage context data maintainedrelative to the battery in NEB 1 and NEB 2. For example, as part ofexemplary system 63000 shown in FIG. 63, command node 24160 may befurther programmatically configured to be operative to identify themediation response based upon the secondary level of battery-relatedanomaly monitoring as well as upon usage context data related to thesubset of batteries (e.g., the batteries in NEB 1 and NEB 2). In oneembodiment, such usage context data may indicate an active usage statusof the particular battery. Examples of such an active usage status maybe a present battery charging state (e.g., a standby state, a chargingstate, and a discharging state) or a current battery health state (e.g.,charge cycle count, delivered voltage, internal resistance, currentcharge capacity, and the like).

In some embodiments, the wireless nodes disposed with the batteries inNEB 1 and NEB 2 may be deployed with a power sensor (e.g., a type ofsensor 360 connected to a battery, such as sensor 57360 a connected toterminals 57005 and 57010 of battery 57002 shown in FIG. 57). Such apower sensor is operative to detect the active usage status of theparticular one of the batteries. In this situation, the advertisingsignals broadcast by the wireless nodes in system 63000 may includeusage context data indicating the active usage status as detected by thepower sensor and, in some embodiments, may allow command node 24160 toidentify or update the usage context data when wirelessly monitoring theadvertising signals.

In another embodiment, the usage context data may indicate a location ofthe battery used in NEB 1 and NEB 2. For example, the usage context datamay include information on the battery's proximity to other importantitems (e.g., mission critical or sensitive electronics that may bedamaged by smoke or heat) or dangerous/hazardous materials withincontainer 24300 a or situated near the location of NEB 1 or NEB 2 asdisposed within container 24300 a (e.g., materials that may catch fireand cause a larger explosion). The usage context data may indicate arisk factor associated with the location of the NEB 1 battery and a riskfactor associated with the location of the NEB 2 battery—e.g.,information on whether that particular battery is within a specificdistance from fuel used by the transit vehicle 24200 so that an anomalywith that battery may cause a larger issue with such fuel (such asflames that may cause a larger explosion). As such, consideration ofusage context data of these types allow command node 24160 todynamically adjust the type of mediation response to automatically andquickly initiate the appropriate mediation response.

A further embodiment of system 63000 as illustrated in FIG. 63 mayinclude multiple wireless nodes disposed with respective differentbatteries (e.g., the ID nodes disposed with each of the batteries in NEB1 and NEB2), multiple secondary sensor-based nodes disposed at differentlocations within the shipping container (e.g., sensor-based ID nodes 1-3located separately within shipping container 24300 a), a command nodeattached to the shipping container (e.g., command node 24160 attached toshipping container 24300 a), and further include an external transceiverin communication with the command node (e.g., exemplary externaltransceiver 24150) and disposed external to the shipping container(e.g., external to shipping container 24300 a and disposed on transitvehicle 24200).

In this further embodiment of system 63000, command node 24160 isprogrammatically configured (via program code, such as part of commandnode management and control code 26425 when executing on the processor26400 of command node 24160) to be operative to conduct an initial levelof battery-related anomaly monitoring by being operative to wirelesslymonitor the advertising signals broadcast by each of the wireless nodesfor an unanticipated state of ceased broadcasting associated with atleast one of the wireless nodes according to a communication profilemaintained on the command node for each of the wireless nodes, andwirelessly monitoring the broadcasted environmental sensor data fromeach of the secondary sensor-based nodes; identify an initial level ofthe battery-related environmental anomaly based on the initial level ofbattery-related monitoring when both the unanticipated state of ceasedbroadcasting is detected for at least one of the wireless nodes and themonitored broadcasted environmental sensor data from the secondarysensor-based nodes reflects at least one of the secondary sensor-basednodes detects a first threshold difference change in the environmentalsensor data within the first time period. Command node 24160 is furtherprogrammatically operative, as part of this further embodiment of system63000, to conduct a secondary level of battery-related anomalymonitoring of broadcasts from the secondary sensor-based nodes inresponse to the identified initial level of the battery-relatedenvironmental anomaly over a second time period, and initiate themediation response to the battery-related environmental anomaly basedupon the secondary level of battery-related anomaly monitoring bybroadcasting a layered alert notification to the external transceiver.In response, this further embodiment of system 6300 has the externaltransceiver (e.g., external transceiver 24150) receiving the layeredalert notification and responsively initiating the mediation response tothe battery-related environmental anomaly.

This further embodiment of system 63000 may have command node 24160further programmatically configured to be operative to conduct thesecondary level of battery-related anomaly monitoring by wirelesslymonitoring the advertising signals broadcast by the wireless nodes foran additional unanticipated state of ceased broadcasting in the secondtime period according to the communication profile, and wirelesslymonitoring for additional environmental sensor data from the secondarysensor-based nodes to verify the initial level of the battery-relatedenvironmental anomaly.

This further embodiment of system 63000 may have command node 24160being further programmatically configured to be operative to conduct thesecondary level of battery-related anomaly monitoring by instructingsome or all of the secondary sensor-based nodes to broadcast theirrespective environmental sensor data at a second messaging rate thatexceeds an initial broadcast rate. Such an initial messaging rate forthe secondary sensor-based nodes may be implemented with an initialvalue correlated to an environmental risk associated with one or more ofthe batteries associated with the wireless nodes (e.g., the batteries inNEB 1 and NEB 2) or other batteries within the shipping container 24300a. The second messaging rate may be implemented at a predeterminedhigher messaging rate based upon a type of material existing within oneor more of the batteries associated with the wireless nodes (e.g., thebatteries in NEB 1 and Neb 2) or other batteries within the shippingcontainer 24300 a. In more detail, command node 24160 may, as part ofthe further embodiment of system 63000, be further programmaticallyconfigured to be operative to initiate the mediation response to thebattery-related environmental anomaly in response to the secondary levelof battery-related anomaly monitoring by broadcasting the layered alertnotification to the external transceiver when both another unanticipatedstate of ceased broadcasting is detected and the broadcastedenvironmental sensor data broadcast at the second messaging ratereflects at least the first threshold difference change in theenvironmental sensor data over the second time period.

In this further embodiment of system 63000, command node 24160 may befurther programmatically configured to be operative to conduct thesecondary level of battery-related anomaly monitoring by being operativeto wirelessly monitor the advertising signals broadcast by the wirelessnodes (e.g., those wireless nodes in each of NEB 1 and NEB 2) for anadditional unanticipated state of ceased broadcasting in the second timeperiod according to the communication profile maintained on the commandnode, wirelessly monitor for additional environmental sensor data fromthe secondary sensor-based nodes to verify the initial level of thebattery-related environmental anomaly, and identify the secondary levelof battery-related anomaly when both another unanticipated state ofceased broadcasting is detected and the broadcasted environmental sensordata reflects at least a second threshold difference change in theenvironmental sensor data over the second time period, wherein thesecond threshold difference change is greater than the first thresholddifference change.

In this further embodiment of system 63000, the external transceiver maybe implemented by an integrated transceiver interface of an automaticfire suppression system (e.g., transceiver 32010 of fire suppressionsystem 25010). As such, the broadcasted layered alert notification fromcommand node 24160 causes the external transceiver (e.g., transceiver32010) to activate the automatic fire suppression system (e.g., system25010) targeting the container. In another example, the externaltransceiver in this further embodiment of system 63000 may be a displaywhere visual and/or audible messages may be presented. As such, thebroadcasted layered alert notification from command node 24160 may causethe display (e.g., display 40015) on the external transceiver togenerate a message requesting manual fire suppression of the containereither visually, through sound, or via a special alarm generatedreflecting the particular message for a manual fire suppression request;or generate a message requesting preparations to cease transportation ofthe container (e.g., a message that provides guidance to a preferredlocation). In a further example, the broadcasted layered alertnotification from command node 24160 causes the external transceiver(e.g., external transceiver 25010) to activate generate a message toinform an entity associated with the batteries that at least one of thebatteries needs replacement. This may be implemented as a message fromexternal transceiver 25010 to remote server 24100, which may then relaysuch a message to the intended recipient entity about the necessity ofsuch a replacement.

This further embodiment of system 63000 may also make use of batteryspecifier data and usage context data as described above when generatingthe layered alert notification and identifying the appropriate mediationresponse.

In still another embodiment, the command node may monitoring a wirelessnode disposed with at least one of the batteries in a shipping containerwhile also monitoring sensor data generated by the command node's ownsensors (e.g., sensors 26465 on exemplary command node 26000). Thus,rather than monitoring separate sensor-based nodes disposed in thecontainer, the command node relies upon and monitors its ownenvironmental sensors as part of a system for layered initiation of amediation response to an environmental anomaly. FIG. 64 is a diagramillustrating an exemplary system for layered initiation of a mediationresponse to a battery-related environmental anomaly involving anode-enabled battery apparatus, and a command node deployed withmultiple environmental sensors in accordance with an embodiment of theinvention. Referring now to FIG. 64, exemplary system 64000 is shownwith a similar shipping container 24300 a on a transit vehicle 24200having an external transceiver 24150 and an onboard fire suppressionsystem 25010. The shipping container 24300 a shown in FIG. 64 hasexemplary command node 24160 disposed on the container 24300 a (e.g.,attached to, temporarily or permanently fixed to, or integrated as partof container 24300 a) and wireless nodes disposed with each of NEB 1 andNEB 2 (e.g., two of the possible node-enabled batteries that may bemaintained within container 24300 a). Such wireless nodes may bedisposed with the batteries of NEB 1 or NEB 2 by being attached to orintegrated with the respective one of the batteries.

As illustrated in FIG. 64, command node 24160 includes multipleenvironmental sensors (e.g., sensors 1-4) disposed within the containeras part of the command node 24160, even if some or all of such sensorsare remotely coupled back to command node 24160 (e.g., an RFenvironmental sensor that is wirelessly coupled to the processor incommand node 24160 or other wired environmental sensors coupled to theprocessor in command node 24160). The command node 24160 generatesenvironmental sensor data upon environmental conditions at differentlocations within the container 24300 a as sensed by each of theenvironmental sensors 1-4. Command node also has a wirelesscommunication interface with which it can communicate with the wirelessnodes within NEB 1 and NEB 2.

As part of system 64000, command node 24160 is programmaticallyconfigured to be operative to conduct an initial level ofbattery-related anomaly monitoring by being further operative towirelessly monitor the advertising signals broadcast by the wirelessnode in, for example, NEB 1, for an unanticipated state of ceasedbroadcasting during a first time period according to a communicationprofile maintained on command node 24160 for that wireless node;wirelessly monitor the environmental sensor data generated from thecommand node's sensors 1-4 over the first time period; and identify aninitial level of the battery-related environmental anomaly based on theinitial level of battery-related monitoring when both the unanticipatedstate of ceased broadcasting is detected and the monitored broadcastedenvironmental sensor data reflects at least a first threshold differencechange in the environmental sensor data. Command node 24160, as part ofsystem 64000, is also programmatically configured to be operative toconduct a secondary level of battery-related anomaly monitoring over asecond time period of at least the environmental sensor data generatedby sensors 1-4 in response to the identified initial level of thebattery-related environmental anomaly, and initiate the mediationresponse to the battery-related environmental anomaly based upon thesecondary level of battery-related anomaly monitoring by broadcasting alayered alert notification.

In a further embodiment of system 64000, command node 24160 may befurther configured to be operative to conduct the secondary level ofbattery-related anomaly monitoring by wirelessly monitoring theadvertising signals broadcast by the wireless node in NEB 1, forexample, for an additional unanticipated state of ceased broadcastingover the second time period according to the communication profilemaintained on command node 24160 for NEB 1, and wirelessly monitoringfor additional environmental sensor data from the environmental sensors1-4 over the second time period to verify the initial level of thebattery-related environmental anomaly.

In still another embodiment of system 64000, command node 24160 may befurther programmatically configured to be operative to conduct thesecondary level of battery-related anomaly monitoring by generating theenvironmental sensor data at a second detection rate that exceeds aninitial detection rate (e.g., a rate set at an initial value correlatedto an environmental risk associated with one or more of the batteries onthe shipping container). The second detection rate may be apredetermined higher detection rate based upon a type of materialexisting within one or more of the batteries on the shipping container.For example, the command node may be further programmatically configuredto be operative to initiate the mediation response to thebattery-related environmental anomaly in response to the secondary levelof battery-related anomaly monitoring by broadcasting the layered alertnotification when both (a) another unanticipated state of ceasedbroadcasting is detected over the second time period and (b) themonitored environmental sensor data detected by sensors 1-4 over thesecond time period at the second detection rate reflects at least thefirst threshold difference change in the environmental sensor data overthe second time period.

In another embodiment of system 64000, command node 24160 may be furtherprogrammatically configured to be operative to conduct the secondarylevel of battery-related anomaly monitoring by being operative towirelessly monitor the advertising signals broadcast by the system'swireless node (e.g., the ID node in NEB 1) for an additionalunanticipated state of ceased broadcasting over the second time periodaccording to the communication profile; wirelessly monitor foradditional environmental sensor data from sensors 1-4 over the secondtime period to verify the initial level of the battery-relatedenvironmental anomaly; and identify the secondary level ofbattery-related anomaly when both another unanticipated state of ceasedbroadcasting is detected during the second time period and thebroadcasted environmental sensor data reflects at least a secondthreshold difference change in the environmental sensor data (where thesecond threshold difference change is greater than the first thresholddifference change).

In embodiments of system 64000, similar to the other embodimentsdescribed above, there may be different types of initiated mediationresponses based on the broadcasted layered alert notification. Forexample, the broadcasted layered alert notification from command node24160 may cause activation of an automatic fire suppression systemtargeting the container (e.g., fire suppression system 25010). Inanother example, the broadcasted layered alert notification from commandnode 24160 may be a message requesting manual fire suppression for thecontainer, a message requesting preparations to cease transportation ofthe batteries within the container (such as guidance to a preferredlocations), or a message to inform an entity associated with thebatteries that the at least one battery needs replacement as describedin more detail above relative to system 63000 and its variousembodiments.

Embodiments of system 64000 may also make use of battery specifier dataand usage context data as described above when generating the layeredalert notification and identifying the appropriate mediation response.

Backup Validation of Detected Environmental Anomaly

Additional embodiments have the capability of validating or verifying adetected environmental anomaly before acting upon such a detected issueto issue alerts or notifications that cause or initiate appropriatemediation responses. This may help prevent issues of a particularcommand node begins to malfunction, especially as the command node maybe disposed within the shipping container where such an environmentalanomaly may occur. For example, a command node's wireless communicationinterface may begin to fail which may otherwise indicate wireless nodesaround the command node being monitored appear to cease broadcasting. Ifthe command node's wireless communication was normally operating, nolonger detecting wireless nodes broadcasting when they are anticipatedto be broadcasting may indicate the presence of an environmental anomaly(e.g., fire) within the command node's shipping container. But with thecommand node's wireless communication beginning to fail, there may be noenvironmental anomaly and simply the wireless communication interface isbroken. Thus, by deploying an enhanced shipping container with multiplecommand nodes (a primary that conducts what may be considered primarymonitoring, and a secondary that conducts a verification of what theprimary has detected to be an environmental anomaly where either or bothmay be deployed with their own respective command node sensors) itselfor as part of a system, embodiments described below help avoid suchmistaken detections of environmental anomalies. Further embodiments mayuse redundant transceivers as part of the wireless communicationinterface in a shipping container's command node where one transceiverperforms the primary monitoring operation and the second transceiver mayperform the verification operation to ensure there was no issue with thefirst transceiver that detected an environmental anomaly.

FIG. 65 is a diagram illustrating an exemplary enhanced system fordetecting and verifying an environmental anomaly within an improvedshipping container having primary and secondary command nodes inaccordance with an embodiment of the invention. Referring now to FIG.65, exemplary system 65000 is shown with similar components as system44000 in FIG. 44 (e.g., transit vehicle 24200, remote server 24100,network 24015, external transceiver 24150, onboard fire suppressionsystem 25010, and shipping container 24300 a), but FIG. 65 illustratesthe exemplary shipping container 24300 a as housing multiple commandnodes (e.g., command node 1 also referenced as 24160 a, command node 2also referenced as 24160 b) and sensor-based ID nodes 1-4 shown disposedin different locations within the container 24300 a.

In more detail, sensor-based ID nodes 1-2 are shown disposed on thebottom floor of shipping container 24300 a (sitting freely or attached)while sensor-based ID node 3 is integrated as part of the container24300 a on a wall of the container. Sensor-based ID node 4 is associatedwith (e.g., attached to or disposed within) package 2 24400 b as shownin FIG. 65. As implementations of an exemplary ID node 120 a having oneor more sensors 360, each of sensor-based ID nodes 1-4 shown in FIG. 65has an ID node processor, an environmental sensor, and a wireless radiotransceiver (which may be implemented as a software defined radio(SDR)). The ID node's sensor is coupled to the ID node processor andgenerates sensor data related to an environmental condition proximatethe respective sensor-based ID node within the shipping container. Thewireless radio transceiver is also coupled to the ID node processor andoperative to broadcast signals that include the sensor data in responseto a command from the ID node's processor. As such, each of thesensor-based ID nodes 1-4 shown in FIG. 65 generate sensor data from andabout the environment proximate their respective locations withinshipping container 24300 a.

Each of command node 1 and command node 2 shown in FIG. 65 may beimplemented similarly to that explained above relative to exemplarycommand node 26000, where each command node has at least a command nodeprocessor coupled to one or more communications interfaces and may alsoinclude one or more environmental sensors so that the respective commandnode may monitor its own generated sensor data as well as the sensordata from monitored sensor-based ID nodes. In one embodiment, eachcommand node's communications interface may be operative to communicatewith the sensor-based ID nodes 1-4, the other command node, as well asexternally disposed components, such as external transceiver 24150and/or fire suppression system 25010. However in another embodiment, afirst communication interface may be operative to communicate with eachof the sensor-based ID nodes 1-4 using a first wireless communicationformat compatible with the wireless radio transceiver on each of thesensor-based ID nodes, while a second communication interface isoperative to communicate with the external transceiver associated withthe transit vehicle using a second wireless communication formatcompatible with the external transceiver (as well as other commandnodes). Those skilled in the art will also appreciate the each ofcommand node 1 and command node 2 may be implemented as a master node(e.g., exemplary master node 110 a that may include its own sensors aswell as location circuitry that enables the master node to self-locate).

In operation and as part of an embodiment of system 65000, a first ofthe command nodes in shipping container 24300 a (e.g., command node 1)is programmatically configured via its onboard executing programming(e.g., code that is part of command node control and management code26425 on command node 1) to be operative to detect the sensor databroadcasted from the sensor-based ID nodes 1-4 using the firstcommunication interface on command node, responsively identify theenvironmental anomaly for the shipping container based upon the sensordata detected by command node 1, and transmit a validation request overthe second communication interface of command node 1 to command node 2(where the validation request is a request to verify the environmentalanomaly for the shipping container 24300 a identified by command node1). The second of the command nodes (e.g., command node 2) isprogrammatically configured via its onboard executing programming (e.g.,additional code that is part of command node control and management code26425 on command node 2) to be operative to detect the sensor databroadcasted from the sensor-based ID nodes 1-4 using the firstcommunication interface on command node 2, receive the validationrequest from command node 1, verify the environmental anomaly for theshipping container 24300 a in response to the validation request andbased upon the sensor data detected by command node 2, and broadcast averification message over the second communication interface of commandnode 2 based upon whether the environmental anomaly for the shippingcontainer 24300 a is verified by command node 2. In this way, commandnode 1 and command node 2 advantageous interact to allow for validationof their monitoring and verification of the environmental anomalydetected prior to sending out the verification message, which caninitiate a mediation response.

In more detail, the exemplary system 65000 may have command node 2broadcasting the verification message as a validated alert notification(e.g., an instruction) to the external transceiver 24150 to cause theexternal transceiver 24150 to initiate a mediation response to theenvironmental anomaly. In one example, the mediation response may causethe external transceiver 24150 to generate a secondary mediationresponse notification for an operator of the transit vehicle as atargeted mediation recipient (e.g., a prompted visual or audible messagegenerated as the second mediation response notification requesting theoperator of the transit vehicle to alter movement of the transit vehicle24200). In another example, the mediation response may cause theexternal transceiver 24150 to generate a similar type of secondarymediation response notification for a logistics crew member of thetransit vehicle 24200 as a targeted mediation recipient (e.g., aprompted visual or audible message generated as the secondary mediationresponse notification requesting the logistics crew member to inspectthe enhanced shipping container 24300 a). In still another example, themediation response may cause the external transceiver 24150 to generatea secondary mediation response notification that activates firesuppression system 25010 within the transit vehicle 24200 and outsidethe shipping container 24300 a.

In an embodiment of system 65000, it may be the first command node thatnotifies the external transceiver. For example, command node 2 maybroadcast the verification message by transmitting the verificationmessage to command node 1, which is further programmatically configuredto transmit a validated alert notification over the second communicationinterface of command node 1 in response to receipt of the verificationmessage from command node 2. With command node 1 transmitting thevalidated alert notification (as an instruction) to the externaltransceiver 24150, command node 1 may cause the external transceiver24150 to initiate a mediation response to the environmental anomaly. Assuch and in one example, the mediation response may cause the externaltransceiver 24150 to generate a secondary mediation responsenotification for an operator of the transit vehicle as a targetedmediation recipient, where the second mediation response notificationrequests the operator of the transit vehicle to alter movement of thetransit vehicle 24200. In another example, the mediation response causesthe external transceiver 24150 to generate a secondary mediationresponse notification for a logistics crew member of the transit vehicleas a targeted mediation recipient (where the secondary mediationresponse notification requests the logistics crew member to inspect theenhanced shipping container 24300 a). In still another example, themediation response may cause the external transceiver 24150 to generatea secondary mediation response notification that activates firesuppression system 25010 within the transit vehicle 24200 and outsidethe shipping container 24300 a.

An embodiment of system 65000 may have command node 1 being furtherconfigured to responsively identify the environmental anomaly for theshipping container 24300 a when (a) the broadcasted sensor data detectedby command node 1 does not include sensor data from at least a thresholdnumber of the sensor-based ID nodes 1-4 and (b) the broadcasted sensordata detected by command node 1 indicates an environmental conditionthat exceeds an environmental threshold maintained by command node 1.Likewise, further details on how command node 2 verifies theenvironmental anomaly as part of an embodiment of system 65000 may havecommand node 2 being further configured to responsively verify theenvironmental anomaly for the shipping container 24300 a when (a) thebroadcasted sensor data detected by command node 2 does not includesensor data from at least a threshold number of the sensor-based IDnodes and (b) the broadcasted sensor data detected by the command node 2indicates an environmental condition that exceeds an environmentalthreshold maintained by command node 2.

When command node 2 is verifying the environmental anomaly, anembodiment may adjust messaging rates as a way to adjust data qualityand refine the verification process. For example, an embodiment may haveeach of sensor-based ID nodes 1-4 maintaining a broadcast profile thatdefines a first messaging rate and a second messaging rate (where firstmessaging rate is slower than the second messaging rate). These twomessaging rates may regulate how often the sensor data generated by arespective sensor-based ID node is broadcast. Command node 1 may befurther operative to detect the sensor data broadcasted from thesensor-based ID nodes 1-4 using the first messaging rate. However, inthis embodiment, command node 2 may be further operative to verify theenvironmental anomaly in response to the validation request byinstructing each of the sensor-based ID nodes 1-4 to broadcast futuregenerated sensor data at the second messaging rate, detect the sensordata broadcasted from the sensor-based ID nodes 1-4 using the secondmessaging rate over the first communication interface on command node 2,and verify the environmental anomaly for the shipping container basedupon the sensor data detected by the second of the command nodesbroadcast by the sensor-based ID nodes using the second messaging rate.

Rather than using multiple command nodes (such as command node 1 andcommand node 2), another system embodiment may provide similarverification functionality by using multiple transceivers within aparticular command node where one transceiver does the primarymonitoring and the other transceiver performs a type of redundantverification. For example, such an embodiment may generally includemultiple sensor-based ID nodes (e.g., ID nodes 1-4 shown in FIG. 65) anda multi-transceiver equipped command node (e.g., exemplary command node24160 a or command node 1 shown in FIG. 65). The sensor-based ID nodes1-4 as similarly configured as described above. In this embodiment,command node 1 is mounted to the shipping container 24300 a (as shown inFIG. 65), and includes at least a processor and two communicationinterfaces coupled to the processor. The first communication interfacehas a first transceiver and a second transceiver where both areoperative to communicate with each of the sensor-based ID nodes 1-4using a first wireless communication format compatible with the wirelessradio transceiver on each of the sensor-based ID nodes. The secondcommunication interface is operative to communicate with the externaltransceiver 24150 associated with the transit vehicle 24200 using asecond wireless communication format compatible with the externaltransceiver 24150 (and command node 2).

In operation and as part of this additional embodiment, command node 1is programmatically configured to be operative to detect the sensor databroadcasted from the sensor-based ID nodes 1-4 using the firsttransceiver of the first communication interface on command node 1;responsively identify the environmental anomaly for the shippingcontainer 24300 a based upon the sensor data detected using the firsttransceiver of the first communication interface on command node 1;verify the environmental anomaly for the shipping container based uponthe sensor data as detected by the second transceiver of the firstcommunication interface of command node 1; and broadcast a verificationmessage over the second communication interface based upon whether theenvironmental anomaly for the shipping container is verified using thesensor data as detected by the second transceiver of the firstcommunication interface of command node 1. Thus, in this additionalembodiment the same command node performs both the primary monitoringoperating that may detect the environmental anomaly and the verificationprocess using different transceivers on the same command node.

This additional system embodiment may have command node 1 being furtherprogrammatically configured to broadcast the verification message as avalidated alert notification (e.g., an instruction) over the secondcommunication interface to the external transceiver to cause theexternal transceiver 24150 to initiate a mediation response to theenvironmental anomaly. Such a mediation response, for example, may causethe external transceiver 24150 to generate a secondary mediationresponse notification for an operator of the transit vehicle 24200 as atargeted mediation recipient (where the second mediation responsenotification is a prompted visual or audio request for the operator ofthe transit vehicle 24200 to alter movement of the transit vehicle24200). In another example, the mediation response may cause theexternal transceiver 24150 to generate a secondary mediation responsenotification for a logistics crew member of the transit vehicle 24200 asa targeted mediation recipient (where the secondary mediation responsenotification is a prompted visual or audio request for the logisticscrew member to inspect the enhanced shipping container 24300 a). Instill another example, the mediation response may cause the externaltransceiver 24150 to generate a secondary mediation responsenotification that activates fire suppression system 25010 within thetransit vehicle 24200 and outside the shipping container 24300 a.

Further still, the additional system embodiment may have the commandnode 1 identifying the anomaly for the shipping container when (a) thebroadcasted sensor data detected using the first transceiver does notinclude the sensor data from at least a threshold number of thesensor-based ID nodes and (b) the broadcasted sensor data detected usingthe first transceiver indicates an environmental condition that exceedsan environmental threshold. Similarly, this single command node systemembodiment may have command node 1 being further configured to verifythe environmental anomaly for the shipping container when (a) thebroadcasted sensor data detected using the second transceiver does notinclude the sensor data from at least a threshold number of thesensor-based ID nodes and (b) the broadcasted sensor data detected usingthe second transceiver indicates an environmental condition that exceedsan environmental threshold.

When command node 1 is verifying the environmental anomaly in thisadditional system embodiment, a further embodiment may adjust messagingrates as a way to adjust data quality and refine the verificationprocess. For example, a further embodiment may have each of sensor-basedID nodes 1-4 maintaining a broadcast profile that defines a firstmessaging rate and a second messaging rate (where first messaging rateis slower than the second messaging rate). These two messaging rates mayregulate how often the sensor data generated by a respectivesensor-based ID node is broadcast. Command node 1 may be furtheroperative to detect the sensor data broadcasted from the sensor-based IDnodes 1-4 using the first transceiver when the sensor-based ID nodes 1-4broadcast using the first messaging rate. Command node may also beoperative to verify the environmental anomaly in response to thevalidation request by being operative to instruct each of thesensor-based ID nodes 1-4 to broadcast future generated sensor data atthe second messaging rate using the second transceiver; detect thesensor data broadcasted from the sensor-based ID nodes 1-4 at the secondmessaging rate using the second transceiver; and verify theenvironmental anomaly for the shipping container 24300 a based upon thesensor data detected by the second transceiver using the secondmessaging rate.

Still with reference to FIG. 65, an exemplary enhanced shippingcontainer apparatus for detecting and verifying an environmental anomalymay be implemented with exemplary shipping container 24300 a, exemplarysensor-based ID nodes 1-4, and exemplary command nodes 1 and 2. As shownin FIG. 65, exemplary shipping container 24300 a is essentially anenclosure that may have a container base portion, walls coupled to thecontainer base portion along one edge, and a container top portioncoupled to another edge on each of the container walls. As such, thecontainer base portion, the container walls and the container topportion collectively define an interior storage space within container24300 a. And while not specifically shown in FIG. 65, at least one ofthe container walls provides a resealable access closure that providesselective access to the interior storage space so that packages (such aspackage 2 24400 b) or other items (such as ID nodes 1 and 2) may beplaced into or removed from the interior storage space of shippingcontainer 24300 a.

As part of this exemplary enhanced shipping container apparatusembodiment, command node 1 and command node 2 are mounted to shippingcontainer 24300 a (e.g., along the ceiling within container 24300 a).Each of command node 1 and command node 1 include at least a commandnode processor, and a communication interface operatively coupled to thecommand node processor. The communication interface is operative tocommunicate with each of the sensor-based ID nodes 1-4 and operative tocommunicate with the external transceiver 24150 associated with thetransit vehicle 24200. As such, the communication of command nodes 1 and2 may be implemented with a single wireless radio transceiver (e.g.,LPWAN, LTE-M1, NB-IOT, or the like whether implemented in hardware, acombination of hardware and software, or as a software defined radio(SDR)) that is capable of short range communications with thesensor-based ID nodes 1-4 but also capable of longer rangecommunications without sacrificing battery life on the command nodes.

In operation, the command nodes (e.g., command node 1 and command node2) of such an exemplary enhanced shipping container apparatus generallyperform the primary monitoring and detecting operation as well as theverification process. In particular, command node 1 in this apparatusembodiment is programmatically configured to be operative to detect thesensor data broadcasted from the sensor-based ID nodes 1-4 using thecommunication interface on command node 1; responsively identify theenvironmental anomaly for the shipping container 24300 a based upon thesensor data detected by command node 1; and transmit a validationrequest over the communication interface of command node 1 to commandnode 2 (where the validation request is a request to verify theenvironmental anomaly for the shipping container 24300 a identified bycommand node 1). Command node 2, in this apparatus embodiment, isprogrammatically configured to be operative to detect the sensor databroadcasted from the sensor-based ID nodes 1-4 using the communicationinterface on command node 2; receive the validation request from commandnode 1; verify the environmental anomaly for the shipping container24300 a in response to the validation request and based upon the sensordata as detected by command node 2; and broadcast a verification messageover the communication interface of command node 2 based upon whetherthe environmental anomaly for the shipping container 24300 a is verifiedby command node 2. Command node 2 may broadcast the verification messageas a validated alert notification (e.g., an instruction) to externaltransceiver 24150 to cause the external transceiver 24150 to initiate amediation response to the environmental anomaly. The mediation responseinitiated by the external transceiver 24150 may, for example, cause theexternal transceiver 24150 to generate a secondary mediation responsenotification for an operator of the transit vehicle 24200 as a targetedmediation recipient (where the second mediation response notificationmay be a prompted visual or audio request for the operator of thetransit vehicle to alter movement of the transit vehicle). In anotherexample, the mediation response may cause the external transceiver 24150to generate a secondary mediation response notification for a logisticscrew member of the transit vehicle as a targeted mediation recipient,the secondary mediation response notification requesting the logisticscrew member to inspect the enhanced shipping container. In still anotherexample, the mediation response may cause the external transceiver 24150to generate a secondary mediation response notification that activates afire suppression apparatus (e.g., onboard fire suppression system 25010)within the transit vehicle and outside the shipping container.

This exemplary apparatus embodiment may have command node 2 broadcastingthe verification message by first transmitting the verification messageto command node 1, which then transmits a validated alert notification(e.g., an instruction to external transceiver 24150) over thecommunication interface on command node 1 in response to receipt of theverification message from command node 2. As such, the transmittedvalidated alert notification to the external transceiver 24150 causesthe external transceiver 24150 to initiate a mediation response to theenvironmental anomaly. As noted above, the mediation response may causethe external transceiver 24150 to generate a secondary mediationresponse notification for an operator of the transit vehicle as atargeted mediation recipient (where the second mediation responsenotification requests the operator of the transit vehicle to altermovement of the transit vehicle). In another example, the mediationresponse may cause the external transceiver 24150 to generate asecondary mediation response notification for a logistics crew member ofthe transit vehicle as a targeted mediation recipient (where thesecondary mediation response notification requests the logistics crewmember to inspect the enhanced shipping container 24300 a). In stillanother example, the mediation response may cause the externaltransceiver 24150 to generate a secondary mediation responsenotification that activates a fire suppression apparatus (e.g. firesuppression system 25010) within the transit vehicle and outside theshipping container. In a further embodiment, such an externaltransceiver instructed to initiate the mediation response may be atransceiver-equipped fire suppression system. As such, the mediationresponse may directly cause the transceiver-equipped fire suppressionsystem (e.g., fire suppression system 25010 having transceiver 32010) todispense a fire suppression material into the shipping container.

Embodiments of the enhanced shipping container apparatus may providemore details on how to identify the environmental anomaly from thesensor data and how to verify the environmental anomaly from the sensordata. For example, command node 1 as part of such an embodiment may befurther configured to responsively identify the environmental anomalyfor the shipping container when (a) the broadcasted sensor data detectedby command node 1 does not include the sensor data from at least athreshold number of the sensor-based ID nodes and (b) the broadcastedsensor data detected by command node 1 indicates an environmentalcondition that exceeds an environmental threshold. In another example,command node 2 as part of such an embodiment may be further configuredto responsively verify the environmental anomaly for the shippingcontainer when (a) the broadcasted sensor data detected by command node2 does not include the sensor data from at least a threshold number ofthe sensor-based ID nodes and (b) the broadcasted sensor data detectedby command node 2 indicates an environmental condition that exceeds anenvironmental threshold.

As with the system embodiments described above, when verifying theenvironmental anomaly, the enhanced shipping container apparatus mayadjust messaging rates as a way to adjust data quality and refine theverification process. For example, each of sensor-based ID nodes 1-4 maymaintain a broadcast profile that defines a first messaging rate and asecond messaging rate (where first messaging rate is slower than thesecond messaging rate). These two messaging rates may regulate how oftenthe sensor data generated by a respective sensor-based ID node isbroadcast. Command node 1 may be further operative to detect the sensordata broadcasted from the sensor-based ID nodes 1-4 using the firstmessaging rate. Command node 2, in this embodiment, may be furtheroperative to verify the environmental anomaly in response to thevalidation request by being operative to instruct each of thesensor-based ID nodes 1-4 to broadcast future generated sensor data atthe second messaging rate; detect the sensor data broadcasted from thesensor-based ID nodes 1-4 using the second messaging rate using thecommunication interface on command node 2; and verify the environmentalanomaly for the shipping container 24300 a based upon the sensor datadetected by command node 2 and broadcast by the sensor-based ID nodes1-4 using the second messaging rate.

In still another embodiment, the enhanced shipping container apparatusmay have at least one of the sensor-based ID nodes be an integratedsensor-based ID node (e.g., exemplary sensor-based ID node 3 as shown inFIG. 65) located on the shipping container 24300 a as part of some partof the container 24300 a (e.g., the floor/base, walls, ceiling, door,etc.)

Yet another embodiment focuses on the operation of such an enhancedshipping container apparatus as a method for detecting and verifying anenvironmental anomaly. FIG. 66 is a flow diagram illustrating anexemplary enhanced method for detecting and verifying an environmentalanomaly related to a shipping container (e.g., shipping container 24300a) using a first command node (e.g., command node 1) mounted to theshipping container, a second command node (e.g., command node 2) mountedto the shipping container, and a plurality of sensor-based ID nodes(e.g., sensor equipped ID nodes 1-4 shown disposed in differentlocations within the shipping container 24300 a) in accordance with anembodiment of the invention. Referring now to FIG. 66, exemplary method6600 is described as starting at step 6605 where the first command nodeis detecting sensor data generated by and broadcast from thesensor-based ID nodes 1-4. At step 6610, method 6600 proceeds withdetecting, by the second command node (command node 2), the sensor datagenerated and broadcast from the sensor-based ID nodes 1-4. As such,steps 6605 and 6610 collectively have each of command nodes 1 and 2independently monitoring sensor data generated and broadcast by thesensor-based ID nodes 1-4 disposed in different locations of shippingcontainer 24300 a.

Primary monitoring operations by the first command node (command node 1)involves steps 6615 and 6620. As such, at step 6615, method 6600proceeds with responsively identifying, by the first command node(command node 1), the environmental anomaly for the shipping containerbased upon the sensor data detected by the first command node. In moredetail, step 6615 may have the first command node identifying theenvironmental anomaly for the shipping container in a multi-mode mannerwhen (a) the broadcasted sensor data detected by the first command nodedoes not include the sensor data from at least a threshold number of thesensor-based ID nodes and (b) the broadcasted sensor data detected bythe first command node indicates an environmental condition that exceedsan environmental threshold.

At step 6620, method 6600 proceeds with transmitting, by the firstcommand node, a validation request to the second command node (commandnode 2). The validation request is a request to verify the environmentalanomaly for the shipping container identified by the first command node.At step 6625, method 6600 proceeds with the second command nodereceiving the validation request from the first command node so that thesecond command node may begin the verification process.

At decision step 6630, method 6600 has the second command nodedetermining if the environmental anomaly is verified. If not, step 6630proceeds directly back to steps 6605 and 6610 where further sensor datais detected by the first and second command nodes. However, if theenvironmental anomaly is verified (i.e., the second command node(command node 2) verifies the environmental anomaly for the shippingcontainer in response to the validation request and based upon thesensor data detected in step 6610 by the second command node), step 6630proceeds to step 6635. In more detail, step 6630 may have the secondcommand node determining such a verification by responsively verifyingthe environmental anomaly for the shipping container also in amulti-mode manner when (a) the broadcasted sensor data detected by thesecond command node does not include the sensor data from at least athreshold number of the sensor-based ID nodes and (b) the broadcastedsensor data detected by the second command node indicates anenvironmental condition that exceeds an environmental threshold.

At step 6635, method 6600 proceeds with broadcasting, by the secondcommand node, a verification message based upon whether theenvironmental anomaly for the shipping container is verified by thesecond command node.

A further embodiment of method 6600 may have step 6635 transmitting, bythe second command node, a validated alert notification to an externaltransceiver to cause the external transceiver to initiate a mediationresponse to the environmental anomaly. Such a validated alertnotification may be implemented as an instruction to cause the externaltransceiver to initiate the mediation response to the environmentalanomaly. Such a mediation response, for example, may cause the externaltransceiver to generate a secondary mediation response notification foran operator of the transit vehicle as a targeted mediation recipient,the second mediation response notification requesting the operator ofthe transit vehicle to alter movement of the transit vehicle. In anotherexample, the mediation response may cause the external transceiver togenerate a secondary mediation response notification for a logisticscrew member of the transit vehicle as a targeted mediation recipient,the secondary mediation response notification requesting the logisticscrew member to inspect the enhanced shipping container. In still anotherexample, the mediation response may cause the external transceiver togenerate a secondary mediation response notification that activates afire suppression system (e.g., fire suppression system 25010) thattargets the shipping container.

In another embodiment of method 6600, step 6635 may be implemented bytransmitting, by the second command node, the verification message tothe first command node, which then further has method 6600 transmitting,by the first command node, a validated alert notification to an externaltransceiver in response to receipt of the verification message from thesecond command node and to cause the external transceiver to initiate amediation response to the environmental anomaly. Such a validated alertnotification may be an instruction to cause the external transceiver toinitiate the mediation response to the environmental anomaly. Theinitiated mediation response may, for example, cause the externaltransceiver to generate a secondary mediation response notification foran operator of the transit vehicle as a targeted mediation recipient(where the second mediation response notification requests the operatorof the transit vehicle to alter movement of the transit vehicle). Inanother example, the initiated mediation response may cause the externaltransceiver to generate a secondary mediation response notification fora logistics crew member of the transit vehicle as a targeted mediationrecipient (where the secondary mediation response notification requeststhe logistics crew member to inspect the enhanced shipping container).In still another example, the initiated mediation response may cause theexternal transceiver to generate a secondary mediation responsenotification that activates a fire suppression system (e.g., system25010) within the transit vehicle and outside the shipping container.

In some embodiments of method 6600, the step of transmitting thevalidated alert notification to the external transceiver further may beaccomplished by transmitting the validated alert notification to atransceiver-equipped fire suppression system as the external transceiver(e.g., system 25010 being equipped with its own transceiver 32010 asshown in FIG. 32C and capable of communication with the command nodes asshown in FIG. 65). Such a validated alert notification may be aninstruction for the transceiver-equipped fire suppression system toactivate and dispense fire suppression material into the shippingcontainer.

Still further embodiments of method 6600 may have the step of detectingthe sensor data by the first command node in step 6605 be implemented asdetecting, by the first command node, the sensor data as broadcast fromthe sensor-based ID node at a first messaging rate, where the firstmessaging rate and a second messaging rate being defined in a broadcastprofile maintained on each of the sensor-based ID nodes, and where eachof the first messaging rate and the second messaging rate regulates howoften the sensor data generated by a respective sensor-based ID node isbroadcast. As part of this embodiment, the first messaging rate isslower than the second messaging rate. As such, the step of verifyingthe environmental anomaly in response to the validation request as partof step 6630 may be implemented as instructing, by the second commandnode, each of the sensor-based ID nodes to broadcast future generatedsensor data at the second messaging rate; detecting, by the secondcommand node, the sensor data broadcasted from the sensor-based ID nodesusing the second messaging rate; and verifying, by the second commandnode, the environmental anomaly for the shipping container based uponthe sensor data detected by the second command node and broadcast by thesensor-based ID nodes using the second messaging rate.

Autonomous Mediation Involving Secure & Trusted Node Interactions

While an exemplary environmental anomaly may be fire within a shippingcontainer or within a package on a shipping container, those skilled inthe art will appreciate than an environmental anomaly may generallyinclude a wide variety of arising conditions that are dangerous whenrelated to a shipping container and especially when the shippingcontainer is being transported on a transit vehicle, such as anaircraft. For example, an environmental anomaly may present emergencyconditions with intense and rapidly spreading harmful, toxic, orotherwise dangerous conditions (e.g., caustic chemical reactionsreleasing toxic fumes that may be detected by sensors; explosions thatmay rapidly spread within a container; extremely flammable goodsigniting, combusting, and spreading within the container; or highlycombustible fuel vaporizing and catching fire). In such emergencyconditions, components used as part of systems and methods that detectand respond to such environmental anomalies may need to quickly andautonomously work in a trusted mode. This may, for example, involvecomponents that validate the communicating/alert issuing device or dataitself broadcast from the device, secure communications between devices(e.g., those broadcasting sensor data and those monitoring/reportingbased on such sensor data), and components with an overall ability toestablish trusted machine-to-machine (M2M) associations or partners inthe context of systems and methods that detect and respond to suchenvironmental anomalies. In a particular example, this may include usingparticular trusted/known sensors (e.g., sensor-based ID nodes) to avoida situation where a shipping container may contain other sensors ordevices that may attempt to spoof the monitoring device (e.g., commandnodes) into relying upon the untrusted sensor and device, which mayintentionally cease broadcasting to trigger a mediation response underfalse pretenses. As a way of achieving such autonomy where speed may beachieved without reliance upon delayed device-to-device interactions(e.g., delays or lags when the monitoring device has to confirmconnections with a server request for credentials), the monitoringdevice may locally cache credentials for connecting with nodes in itsvicinity as part of such systems and methods that detect and respond tosuch environmental anomalies. Such systems and methods may also, in someembodiments, involve validation of the message itself as alternative orin addition to validating the device broadcasting the message (e.g., asensor-based ID node broadcasting signals having sensor data that may bemonitored by a command node).

FIG. 67 is a diagram illustrating an exemplary system for securelymonitoring a shipping container for an environmental anomaly usingelements of a wireless node network that interact with an externaltransceiver associated with a transit vehicle having at least temporarycustody of the shipping container in accordance with an embodiment ofthe invention. Referring now to FIG. 67, exemplary system 67000 is shownwith similar components as system 65000 in FIG. 65 (e.g., transitvehicle 24200, remote server 24100, network 24015, external transceiver24150, onboard fire suppression system 25010, and shipping container24300 a), but FIG. 67 illustrates the exemplary shipping container 24300a as housing one command node (e.g., command node 1 also referenced as24160 a) and sensor-based ID nodes 1-4 shown disposed in differentlocations within the container 24300 a.

In more detail, sensor-based ID nodes 1-2 are shown in FIG. 67 beingdisposed on the bottom floor of shipping container 24300 a (sittingfreely or attached) while sensor-based ID node 3 is integrated as partof the container 24300 a on a wall of the container. Sensor-based IDnode 4 is associated with (e.g., attached to or disposed within) package2 24400 b as shown in FIG. 67. As implementations of an exemplary IDnode 120 a having one or more sensors 360, each of sensor-based ID nodes1-4 shown in FIG. 67 has an ID node processor, an environmental sensor,and a wireless radio transceiver (which may be implemented in hardware,in a combination of hardware/software/or as a software defined radio(SDR)). The environmental sensor in each ID node is coupled to the IDnode processor and generates sensor data related to an environmentalcondition proximate the respective sensor-based ID node within theshipping container. The wireless radio transceiver is also coupled tothe ID node processor and operative to broadcast signals that includethe sensor data (in additional to a validation record used to confirmthe sensor data broadcast as part of the signal is from that particularID node) in response to a command from the ID node's processor. As such,each of the sensor-based ID nodes 1-4 shown in FIG. 67 generate sensordata from and about the environment proximate their respective locationswithin shipping container 24300 a.

Exemplary command node 1 illustrated in FIG. 67 may be implementedsimilarly to that explained above relative to exemplary command node26000, where the command node has at least a command node processorcoupled to one or more wireless transceiver-based communicationsinterfaces as well as a command node memory. In one embodiment, thecommand node's communications interface may be operative to communicatewith sensor-based ID nodes 1-4 as well as externally disposedcomponents, such as external transceiver 24150 and/or fire suppressionsystem 25010. However in another embodiment with multiple communicationinterfaces, a first communication interface may be operative tocommunicate with each of sensor-based ID nodes 1-4 using a wirelesscommunication format compatible with the wireless radio transceiver oneach of sensor-based ID nodes 1-4, while a second communicationinterface is operative to communicate with the external transceiver24150 associated with the transit vehicle 24200 using a second wirelesscommunication format compatible with the external transceiver (as wellas other command nodes that may be disposed on the transit vehicle 24200in other shipping containers). Those skilled in the art will alsoappreciate command node 1 may be implemented as a master node (e.g.,exemplary master node 110 a that may include its own sensors as well aslocation circuitry that enables the master node to self-locate) or acontainer node that may not have location circuitry. Further, commandnode 1 may be integrated as part of the shipping container 24300 a or beimplemented separately (as a separate device) but removably mounted tothe shipping container 24300 a.

The memory on command node 1 as shown in the embodiment illustrated inFIG. 67 may store and maintain at least command node containermanagement program code (e.g., code that is part of command node controland management code 26425 on command node 1), security credentials 67435specific to one from a subset of sensor-based ID nodes 1-4 that are tobe trusted (e.g., a type of security data 435 explained generallyabove), a primary list of sensors 67005, and association data 67440(e.g., a type of association data 440 explained above). Such informationon the memory of command node 1 may be initially downloaded from orprovided by external transceiver 24150 (as a type of master node thatmay periodically update nodes lower in the network), which may obtainsuch information initially from remote server 24100 that may manage suchinformation (e.g., authorize what devices are trusted sensors viaestablishing the security credentials 67435, generating the primary listof sensors 67005, and authorizing any associations reflected byassociation data). In more detail, an command node may include therequisite security credentials on which devices are to be trusted at thetime of manufacture, thus allowing the command node to validate thesensor-based ID nodes around the particular command node as secure ortrusted sensors. Alternatively, another example may have the exemplarycommand node obtaining the requisite security credentials 67435, primarylist of sensors 67005, and any authorizations for association from thebackend infrastructure (e.g., external transceiver 24150 and/or remoteserver 24100) so that the exemplary command node may operateautonomously if not in contact with such backend infrastructure.

In operation and as part of an embodiment of system 67000, command node1 is programmatically configured via its onboard executing programming(e.g., the command node container management program code that is partof command node control and management code 26425) to be operative toidentify which of sensor-based ID nodes 1-4 are trusted sensors disposedwithin the shipping container 24300 a based the security credentials67435. Those identified are considered confirmed sensor-based ID nodes(e.g., sensor-based ID nodes 1-3 may have security credentials 67435cached on command node 1 that identify them as trusted sensors and,thus, confirmed sensor-based ID nodes while sensor-based ID node 4 maynot have a corresponding security credential within those stored oncommand node 1). Command node 1 is further programmatically configuredto be operative to monitor, via the wireless transceiver-basedcommunication interface, only the confirmed ones of the sensor-based IDnodes (e.g., ID nodes 1-3) for sensor data broadcast from each of theconfirmed sensor-based ID nodes while disregarding any sensor databroadcast from those of the sensor-based ID nodes not identified asbeing confirmed sensor-based ID nodes; detect the environmental anomalyfor the shipping container based upon the sensor data monitored from atleast one of the confirmed sensor-based ID nodes; automatically generatean alert notification related to the detected environmental anomaly forthe shipping container; and cause the wireless transceiver-basedcommunication interface to transmit the alert notification to theexternal transceiver to initiate a mediation response related to thedetected environmental anomaly. As such, this system embodiment reliesupon the security credentials to ensure only trusted sensors aremonitored when detecting and responding to an environmental anomalyrelated to the shipping container 24300 a.

The processor in command node 1 may, in some embodiments, be furtherprogrammatically configured to download the security credentials 67435(and/or an update for such credentials) and maintain securitycredentials 67435 as cached security credentials on the command nodememory.

Device associations may also be used to identify which of thesensor-based ID nodes are trusted sensors. For example, the command nodeprocessor of command node 1 may be programmatically configured toidentify which of sensor-based ID nodes 1-4 are trusted sensors by beingfurther programmatically configured to be operative to access one of thesecurity credentials 67435 specific to a particular one of sensor-basedID nodes 1-4 to determine whether that sensor-based ID node is one ofthe trusted sensors; and establish a trackable association betweencommand node 1 and that sensor-based ID node by generating associationdata 67440 reflecting the trackable association when the one of thesecurity credentials 67435 specific to the particular one of thesensor-based ID nodes indicates that sensor-based ID node is one of thetrusted sensors. As such, the established trackable association confirmsthat the particular one of the sensor-based ID nodes 1-4 is one of thetrusted sensors and reflects that the particular one of sensor-based IDnodes 1-4 is one of the confirmed sensor-based ID nodes (e.g., one of IDnodes 1-3 given the security credentials 67435). In a furtherembodiment, the trackable association between command node 1 and theparticular one of sensor-based ID nodes 1-4 may reflect a permissivesecure connection between command node 1 and that particularsensor-based ID node over and through which that sensor-based ID nodemay securely broadcast its sensor data. In another example, thetrackable association between command node 1 and the particular one ofthe sensor-based ID nodes may also reflect an authorized logical pairingof the command node and that particular sensor-based ID node. As such,the association data generated in that example indicates the authorizedlogical pairing of command node 1 and that particular one ofsensor-based ID nodes 1-4.

In a further embodiment of such a system, the command node processor ofcommand node 1 may be programmatically configured to access the relevantsecurity credentials by being further programmatically configured to beoperative to generate a security credential request specific to one ofthe sensor-based ID nodes 1-4 when none of the security credentials67435 on the command node memory are specific to that particular one ofsensor-based ID node 1-3. Such a security credential request may betransmitted, for example, to external transceiver 24150 or sent toserver 24100 as a further level of making sure a particular one of thesensor-based ID nodes in shipping container 24300 a may or may not be atrusted sensor and appropriate to monitor when attempting to detect andrespond to an environmental anomaly in shipping container 24300 a.

As noted above, the command node memory on command node 1 may includeand maintain a primary list of sensors 67005 (e.g., as a type ofassociation data 440 related to particular sensors, and which may beupdated from external transceiver 24150). As such, the command nodeprocessor in command node 1 may be programmatically configured toidentify which of sensor-based ID nodes 1-4 are trusted sensors by beingfurther programmatically configured to be operative to access theprimary list of sensors 67005 from the command node memory, compare theprimary list of sensors 67005 against each of the sensor-based ID nodes1-4 (e.g., identification information on each of sensor-based ID nodes1-5 that may be kept as part of sensor data 445) so as to identify aparticular subset of sensor-based ID nodes 1-4 on the primary list ofsensors 67005; and identify which of the subset of the sensor-based IDnodes is confirmed to be one of the trusted sensors based upon thesecurity credentials and the primary list of sensors.

In a further embodiment, such a system may have command node 1validating not only the trusted sensors, but also what sensor data is tobe trusted based on the sensor data and signals sending the sensor data.For example, the command node processor of command node 1 may be furtherprogrammatically configured to be operative to validate the sensor databroadcast from each of the confirmed sensor-based ID nodes (e.g.,confirmed ID nodes 1-3) upon receiving the sensor data broadcast fromeach of the confirmed sensor-based ID nodes, and then detect theenvironmental anomaly for the shipping container based only upon thesensor data validated by command node 1. In more detail, the commandnode processor of command node 1 may be programmatically configured tovalidate the sensor data by being further programmatically configured tocause the wireless transceiver-based communication interface to transmita validation request to one or more of the confirmed sensor-based IDnodes, and then receive (via the wireless transceiver-basedcommunication interface on command node 1) a validation confirmationfrom the respective confirmed sensor-based ID node in response to thevalidation request. Such a validation confirmation indicates that therespective one of the confirmed sensor-based ID nodes receiving thevalidation request previously broadcast at least part of the sensordata.

In still another embodiment, such a system may have the command nodeprocessor of command node 1 being programmatically configured tovalidate the sensor data by being further programmatically configured todetermine which of the sensor data received by the command node duringmonitoring is valid by assessing a validation record within each of thereceived sensor data broadcast from each of the confirmed sensor-basedID nodes without requiring the command node to transmit a validationrequest to each of the confirmed sensor-based ID nodes. For example,command node 1 may monitor a confirmed sensor-based ID node (such as IDnode 1) and receive sensor data from ID node 1. The sensor databroadcast from ID node 1 may include a validation record (e.g., asecurity data structure) that securely reflects and ensures that sensordata from ID node 1 is truly from ID node 1 without incurring the burdenof transmitting a validation request to ID node 1 to ensure it was IDnode 1 that generated the specific sensor data. In a further example,such a security data structure may be implemented as a hash keygenerated by confirmed sensor-based ID node 1 that broadcasts the sensordata received by command node 1. Such a hash key may be used by commandnode 1 as a key into the block or table of sensor data to validatewhether it was confirmed sensor-based ID node 1 that actually generatedthe sensor data sent to command node 1.

Systems may use the sensor data from confirmed sensor-based ID nodes invarious ways when detecting an environment anomaly. For example, thecommand node processor of command node 1 may be programmaticallyconfigured to detect the environmental anomaly when the sensor datamonitored from at least one of the confirmed sensor-based ID nodescomprises temperature sensor data above a threshold value; or when thesensor data monitored from each of the confirmed sensor-based ID nodesidentifies one or more missing confirmed sensor-based ID nodes that areanticipated to be broadcasting; or when the sensor data monitored fromeach of the confirmed sensor-based ID nodes identifies an unanticipatedstate of ceased broadcasting from any (or a threshold number) of theconfirmed sensor-based ID nodes.

Identifying what sensor-based ID nodes are trusted sensors may, in someembodiments, involve vehicle status data provided by the externaltransceiver 24150 associated with transit vehicle 24200. For example,the command node processor of command node 1 may be furtherprogrammatically configured to receive initial or updated vehicle statusdata from the external transceiver 24150 associated with transit vehicle24200, and then identify which of the sensor-based ID nodes is one ofthe trusted sensors based upon one of the security credentials specificto a respective one of the sensor-based ID nodes and upon a state of thetransit vehicle as indicated by the vehicle status data. Such as stateof the transit vehicle, as reflected by the vehicle status data, mayinclude a takeoff vehicular status, a cruising vehicle status, a landingvehicular status, and a stationary vehicular status.

Components from the system embodiment described above and its variationsmay be deployed as operational elements that perform an exemplary methodfor securely monitoring such a shipping container. FIG. 68 is a flowdiagram illustrating an exemplary method for securely monitoring ashipping container for an environmental anomaly based upon confirmedsensor-based ID nodes used as trusted sensors in accordance with anembodiment of the invention. Such an exemplary method 6800 as describedon FIG. 68 generally includes multiple sensor-based ID nodes (e.g., IDnodes 1-4 shown in FIG. 67) disposed within the shipping container(e.g., shipping container 24300 a) and a command node (e.g., commandnode 1) associated with the shipping container and operative tocommunicate with each of the sensor-based ID nodes and an externaltransceiver (e.g., external transceiver 24150) associated with a transitvehicle (e.g., transit vehicle 24200) having at least temporary custodyof the shipping container. The sensor-based ID nodes used as part ofmethod 6800 may have at least one being disposed on part of the shippingcontainer (e.g., ID node 1 shown in FIG. 67 being disposed on a base orfloor of shipping container 24300 a) or affixed to an object beingtransported within the shipping container (e.g., ID node 4 being affixedor attached to package 2 being transported within shipping container24300 a). The command node used as part of method 6800 may beimplemented, for example, as a container node integrated as part of theshipping container or a master node associated with the shippingcontainer and implemented separately from the shipping container whileattached to the shipping container. Further, the transit vehicle used aspart of method 6800 may be, for example, an airplane, a railwayconveyance, a maritime vessel, or a roadway conveyance.

Referring now to FIG. 68, exemplary method 6800 begins at step 6805 withthe command node identifying which of the sensor-based ID nodes is oneof the trusted sensors disposed within the shipping container based upona security credential specific to a respective one of the sensor-basedID nodes, the identified ones of the sensor-based ID nodes beingconfirmed sensor-based ID nodes. Such a security credential may becached on the command node or, in some embodiments, method 6800 may alsohave the command node downloading the security credential and storing asthe cached security credential on the command node. In more detail, anembodiment may have step 6805 identifying which of the sensor-based IDnodes is one of the trusted sensors by having the command node obtainingthe security credential specific to a particular one of the sensor-basedID nodes to determine whether that particular sensor-based ID node isone of the trusted sensors; and establishing an active associationbetween the command node and that particular sensor-based ID node whenthe security credential specific to the particular one of thesensor-based ID nodes indicates that particular sensor-based ID node isone of the trusted sensors. Such an established active associationconfirms that the particular one of the sensor-based ID nodes is one ofthe trusted sensors and reflects that the particular one of thesensor-based ID nodes is one of the confirmed sensor-based ID nodes. Ineven more detail, obtaining the security credential described above mayhave the command node accessing a memory on the command node for acached copy of the security credential specific to the particular one ofthe sensor-based ID nodes, or requesting the security credentialspecific to the particular one of the sensor-based ID nodes from theexternal transceiver (e.g., external transceiver 24150). Such an activeassociation between the command node and the particular one of thesensor-based ID nodes may, for example, reflect a permissive secureconnection between the command node and the particular one of thesensor-based ID nodes over which the particular one of the sensor-basedID nodes securely broadcasts its sensor data. In another example, theactive association between the command node and the particular one ofthe sensor-based ID nodes may reflect an authorized logical pairing ofthe command node and the particular one of the sensor-based ID nodes,where the active association is represented by association datagenerated by the command node and maintained on the command node (e.g.,association data 67440 shown in FIG. 67). Further still, an embodimentmay have step 6805 identifying which of the sensor-based ID nodes is oneof the trusted sensors by the command node generating such associationdata reflecting an authorized logical pairing of the command node and aparticular one of the sensor-based ID nodes when the security credentialspecific to the particular one of the sensor-based ID nodes permits thelogical pairing of the command node and the particular one of thesensor-based ID nodes.

At step 6810, method 6800 proceeds with the command node monitoring onlythe confirmed ones of the sensor-based ID nodes for sensor databroadcast from each of the confirmed sensor-based ID nodes. For example,if the confirmed sensor-based ID nodes include only ID nodes 1-3 and theID node 4 with package 2 has not been identified as being a trustedsensor, then monitoring as part of step 6810 has command node 1 onlymonitoring sensor data broadcast from each of ID nodes 1-3 and only IDnodes 1-3 as those sensor-based ID nodes are the trusted sensorsidentified by command node 1.

At step 6815, method 6800 proceeds with the command node detecting theenvironmental anomaly for the shipping container based upon the sensordata monitored from at least one of the confirmed sensor-based ID nodes.In more detail, an embodiment of step 6815 may have the command nodedetecting the environmental anomaly for the shipping container when thesensor data monitored from the at least one of the confirmedsensor-based ID nodes comprises sensor data (e.g., temperature data,pressure data, and the like) is above a threshold value.

In another example, detecting the environmental anomaly may occur aspart of step 6815 when the sensor data monitored from each of theconfirmed sensor-based ID nodes identifies one or more missing ones ofthe confirmed sensor-based ID nodes. Stated another way, step 6815 mayhave the command node detecting the environmental anomaly for theshipping container when the sensor data monitored from each of theconfirmed sensor-based ID nodes (e.g., ID nodes 1-3) identifies anunanticipated state of ceased broadcasting from any of the confirmedsensor-based ID nodes (e.g., such as when ID node 2 ceasesbroadcasting). In more detail, detecting the environmental anomaly mayhave the command node identifying an unresponsive group from theconfirmed sensor-based ID nodes to be in the unanticipated state ofceased broadcasting based upon the monitoring in step 6810, and thendetect the environmental anomaly for the shipping container when a sizeof the identified unresponsive group from the confirmed sensor-based IDnodes exceeds a threshold setting maintained by the command node.

At step 6820, method 6800 proceeds with the command node automaticallygenerating an alert notification related to the detected environmentalanomaly for the shipping container. Then, at step 6825, method 6800proceeds with the command node transmitting the alert notification tothe external transceiver to initiate a mediation response related to thedetected environmental anomaly (such as generating a prompt message asdescribed above or activating a fire suppression system (e.g., firesuppression system 25010)).

In a further embodiment of method 6800, step 6805 may deploy a two-stageconfirmation using both a primary list of sensors (e.g., primary list ofsensors 67005 maintained on command node 1 that maybe provided andupdated by external transceiver 24150) as well as security credentials(e.g., 67435) maintained on the command node. For example, in such afurther embodiment of method 6800, the step of identifying which of thesensor-based ID nodes is one of the trusted sensors may have the commandnode accessing a primary list of sensors maintained on the command node;comparing the primary list of sensors against each of the sensor-basedID nodes to identify a subset of the sensor-based ID nodes confirmed tobe on the primary list of sensors; and identifying which of the subsetof the sensor-based ID nodes is one of the trusted sensors based uponthe security credential specific to a respective one of the subset ofthe sensor-based ID nodes, where the identified ones from the subset ofthe sensor-based ID nodes being the confirmed sensor-based ID nodes.

In still another further embodiment of method 6800, validation of thesensor data itself may be performed. For example, in this furtherembodiment, method 6800 may also have the command node validating thesensor data broadcast from each of the confirmed sensor-based ID nodesupon receiving the sensor data broadcast from each of the confirmedsensor-based ID nodes. As such, the detecting operation in step 6815 maythen have the command node detecting the environmental anomaly for theshipping container based only upon the sensor data validated by thecommand node. In one example, the validating step may involve having thecommand node transmitting a validation request to a respective one (orall) of the confirmed sensor-based ID nodes, and receiving a validationconfirmation from the respective one (or all) of the confirmedsensor-based ID nodes in response to the validation request. Such avalidation confirmation indicates that the respect one (or each) of theconfirmed sensor-based ID nodes receiving the validation requestpreviously broadcast at least part of the sensor data.

In another example, the validating step may involve having the commandnode determining which of the sensor data received by the command nodeduring monitoring is valid by assessing a validation record within eachof the received sensor data broadcast from each of the confirmedsensor-based ID nodes without requiring the command node to transmit avalidation request to each of the confirmed sensor-based ID nodes. Sucha validation record may be implemented as a security data structure(e.g., a hash key as generally described above) with which the commandnode can process to ensure one of the confirmed sensor-based ID nodesgenerated the sensor data monitored and received by the command node.

A further embodiment of method 6800 may have the command node receivingvehicle status data provided by the external transceiver associated withthe transit vehicle. As such, the identifying operation of step 6805 maybe performed by having the command node identifying which of thesensor-based ID nodes is one of the trusted sensors disposed within theshipping container based upon (a) the security credential specific tothe respective one of the sensor-based ID nodes and (b) a state of thetransit vehicle as indicated by the vehicle status data (e.g., where thestate of the transit vehicle may be a takeoff vehicular status, acruising vehicle status, a landing vehicular status, and a stationaryvehicular status).

FIG. 69 is a flow diagram illustrating an alternative exemplary methodfor securely monitoring a shipping container for an environmentalanomaly based upon confirmed sensor data used as trusted sensor data inaccordance with an embodiment of the invention. Such an exemplary method6900 as described on FIG. 69 generally includes multiple sensor-based IDnodes (e.g., ID nodes 1-4 shown in FIG. 67) disposed within the shippingcontainer (e.g., shipping container 24300 a) and a command node (e.g.,command node 1) associated with the shipping container and operative tocommunicate with each of the sensor-based ID nodes and an externaltransceiver (e.g., external transceiver 24150) associated with a transitvehicle (e.g., transit vehicle 24200) having at least temporary custodyof the shipping container. The sensor-based ID nodes used as part ofmethod 6900 may have at least one being disposed on part of the shippingcontainer (e.g., ID node 1 shown in FIG. 67 being disposed on a base orfloor of shipping container 24300 a) or affixed to an object beingtransported within the shipping container (e.g., ID node 4 being affixedor attached to package 2 being transported within shipping container24300 a). The command node used as part of method 6900 may beimplemented, for example, as a container node integrated as part of theshipping container or a master node associated with the shippingcontainer and implemented separately from the shipping container whileattached to the shipping container. Further, the transit vehicle used aspart of method 6900 may be, for example, an airplane, a railwayconveyance, a maritime vessel, or a roadway conveyance.

Referring now to FIG. 69, exemplary method 6900 begins at step 6905 withthe command node (e.g., command node 1 shown in FIG. 67) monitoringsignals broadcast from each of the sensor-based ID nodes (e.g.,sensor-based ID nodes 1-4 shown in FIG. 67) where the monitored signalsinclude sensor data generated from each of the sensor-based ID nodes.

At step 6910, method 6900 has the command node identifying which of thesensor data is trusted sensor data based upon validation data includedwithin each of the respective monitored signals that includes the sensordata. In more detailed example, identifying which of the sensor data istrusted sensor data may have the command node assessing a validationrecord as part of the validation data and doing so without requiring thecommand node to transmit a validation request to each of thesensor-based ID nodes.

In still another example, an embodiment of step 6910 may have thecommand node identifying which of the sensor data is trusted sensor databy accessing a file or data structure representing a primary list ofsensors maintained on the command node (e.g., primary list of sensors67005), and comparing the primary list of sensors against the validationdata included with the sensor data in each of the respective signalsbroadcast from the sensor-based ID nodes to identify a subset of thesensor data confirmed to be generated by one from the primary list ofsensors. Such an identified subset of the sensor data is determined, bythe command node, to be the trusted sensor data. In more detail, thevalidation data may be implemented as a security data structure (e.g., ahash key for the validation record as generated by the one of thesensor-based ID nodes that broadcasts the sensor data related to thevalidation data) with which the command node can process to ensure thatthe sensor data related to the validation record was generated by a oneof the sensor-based ID nodes on the primary list of sensors.

At step 6915, method 6900 has the command node detecting theenvironmental anomaly for the shipping container based upon only theidentified trusted sensor data. In more detail, step 6915 may have thecommand node detecting the environmental anomaly for the shippingcontainer when the identified trusted sensor data has at least a portionbeing temperature sensor data above a threshold value. In anotherexample, step 6915 may have the command node detecting the environmentalanomaly when the identified trusted sensor data identifies one or moremissing ones of the sensor-based ID nodes anticipated to be broadcasting(e.g., the missing sensor-based ID nodes anticipated to be broadcastingtrusted sensor data have entered a state of ceased broadcastingunexpectedly).

At step 6920, method 6900 has the command node automatically generatingan alert notification related to the detected environmental anomaly forthe shipping container and then, at step 6925, transmitting the alertnotification to the external transceiver to initiate a mediationresponse related to the detected environmental anomaly (such asgenerating a prompt message as described above or activating a firesuppression system (e.g., fire suppression system 25010)).

Those skilled in the art will appreciate that method 6900 as disclosedand explained above in various embodiments may be implemented using anexemplary system for securely monitoring a shipping container for anenvironmental anomaly such as that explained above with reference toFIG. 67 and its exemplary elements. Such an embodiment of this exemplarysecure monitoring system, as explained above relative to operationsaccording to method 6900 and with elements from FIG. 67, may use atleast multiple ID nodes disposed within the shipping container (e.g., IDnodes 1-4) running one or more ID node monitoring program code as partof node control and management code 325 to control operations of the IDnodes to generate and broadcast ID node sensor data, as well as acommand node mounted to the shipping container (e.g., command node 24160or command node 1 shown in FIG. 67) running one or more parts of CNcontrol & management code 26425 (e.g., the command node containermanagement program code that is part of command node control andmanagement code 26425) to control the operations of the command node aspart of securely monitoring a shipping container for an environmentalanomaly using the trusted sensor data. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 26415 oncommand node 24160 (also referenced as command node 1, which is anembodiment of exemplary command node 26000) and memory storage 315 on IDnodes 1-4 (embodiments of exemplary ID node 120 a). Thus, when executingsuch code, the ID nodes and the command node may be operative to performoperations or steps from the exemplary methods disclosed above,including method 6900 and variations of that method.

Node-Enhanced Detection Blanket

While the embodiments described above had ID nodes disposed within theshipping container, further embodiments may have ID nodes integrated aspart of a blanket-type of structure that may be placed under packages(e.g., prior to loading packages into a shipping container) or may bequickly added as packages are loaded to deploy an arrangement of IDnodes (e.g., a geographically dispersed group of ID nodes distributed indifferent locations within the shipping container, even if some of thegroup are close to each other or are on contact with each other) thatmay communicate with the shipping container's command node. Such anode-enhanced/enabled sheet or blanket type of structure (e.g., rigid orflexible) having such integrated ID nodes may be added but kept loosewithin the shipping container in some embodiments, but also may be addedand secured to part of the shipping container to help prevent movementof packages beneath such node-enhanced blanket structure (generallyreferred to here as a detection blanket having integrated ID nodes forenvironmental anomaly detection). In further embodiments, such adetection blanket may be made from fire/heat/chemical/radiationresistant material to help contain any environmental anomaly involvingexposure to fire, intense heat, caustic chemicals, and/or radioactivematerials leaking out from protective packaging. The detection blanket(as well as the enclosure on the integrated ID nodes), in otherembodiments, may be designed to fail or break down at particulartemperatures or under certain environmental conditions indicative oftypes of environmental anomalies. The description that follows and FIGS.70-76 as explained below provide further details of such furtherembodiments.

FIG. 70 is a diagram generally illustrating an exemplary node-enhanceddetection blanket shown in perspective within a cutaway view of anexemplary shipping container in accordance with an embodiment of theinvention. Referring now to FIG. 70, an exemplary system 70000 is shownhaving shipping container 70300 and exemplary detection blanket 70005,which is shown covering and securing packages 70400 within container70300. While exemplary shipping container 70300 is shown in perspectivehaving walls 70305 and base 70310, the cutaway view shown in FIG. 70does not show a top/lid for the container 70300 nor some of the wallsfor purposes of viewing the interior contents more clearly. As disposedwithin shipping container 70300, packages 70400 are secured by theexemplary detection blanket 70005, which is connected to the container70300 at attachment points 70010 using tie-down straps 70015. While notshown in FIG. 70, exemplary detection blanket 70005 has multipleintegrated nodes that may be sensor-based nodes (e.g., ID node devicesthat generate and broadcast sensor data) or nodes that simply broadcastadvertising signals periodically so as to be detected by a command nodemounted to the shipping container (not shown in FIG. 70). In general,detection blanket 70005 may be implemented as a single solid panel, agroup of multiple connected panels, or flexible material (e.g., cargonet, webbing, braided net, reinforced tarp, and the like) that areintegrated with one or more ID nodes (such as sensor-based ID nodes) aswill be explained in more detailed examples below.

FIG. 71 provides further details on such nodes integrated into and aspart of different types of exemplary detection blankets. In particular,FIG. 71 is a diagram illustrating an exemplary system for enhanceddetecting of an environmental anomaly relative to packages maintained ina shipping container using multiple types of node-enabled detectionblankets below and above the packages in accordance with an embodimentof the invention. Referring now to FIG. 71, exemplary system 71000 isshown with similar components as system 65000 in FIG. 65 (e.g., transitvehicle 24200, remote server 24100, network 24015, external transceiver24150, onboard fire suppression system 25010, and shipping container24300 a), but FIG. 71 illustrates the exemplary shipping container 24300a as housing a command node (e.g., command node 1 also referenced as24160 as shown in FIG. 71) and packages 1-4 (also referenced as packages24400 a-24400 d). Additionally, FIG. 71 shows two different embodimentsof node-enabled detection blankets 70005 a, 70005 b disposed relative topackages 1-4.

Exemplary node-enabled detection blanket 70005 b is shown as a rigidtype detection blanket disposed at the bottom of shipping container24300 a and including sensor-based ID nodes 71120 e-71120 h integratedas part of the detection blanket 70005 b in a geographically disperseconfiguration relative to the detection blanket so as to cover differentparts of the detection blanket and the areas proximate the respective IDnodes 71120 e-71120 h. As implementations of an exemplary ID node 120 ahaving one or more sensors 360, each of sensor-based ID nodes 71120e-71120 h shown in FIG. 71 as part of exemplary detection blanket 70005b (as well as sensor-based ID nodes 71120 a-71120 d shown in FIG. 71 aspart of exemplary detection blanket 70005 a) has an ID node processor,an environmental sensor, and a wireless radio transceiver (which may beimplemented in hardware, in a combination of hardware/software/or as asoftware defined radio (SDR)). The environmental sensor in each ID nodeis coupled to the ID node processor and generates sensor data related toan environmental condition proximate the respective sensor-based ID nodewithin the shipping container. Such sensor data is indicative of theenvironmental anomaly when the sensor data generated is above athreshold condition for the at least one environmental sensor. Thewireless radio transceiver is also coupled to the ID node processor andoperative to broadcast signals that include the sensor data (inadditional to a validation record used to confirm the sensor databroadcast as part of the signal is from that particular ID node) inresponse to a command from the ID node's processor. Stated another way,the wireless radio transceiver in each of ID nodes 71120 e-71120 h areconfigured to access the sensor data generated by its environmentalsensor and broadcast the sensor data in response to a report commandfrom the ID node processor when the ID node processor executes the IDnode monitoring program code (e.g., code that is part of node controland management code 325 in memory 315, 320 of the ID node). As such,each of the sensor-based ID nodes 71120 e-71120 h integrated as part ofdetection blanket 70005 b shown in FIG. 71 generate sensor data from andabout the environment proximate their respective locations withinshipping container 24300 a.

In general, detection blankets 70005 a, 70005 b as illustrated in FIG.71 have different regions where ID nodes may be integrated as parts ofthe detection blankets. Thus, while ID nodes may be placed closetogether or even touching one another as integrated into parts of thedetection blanket (e.g., where some of the ID nodes may form a sensingarray of nodes), some embodiments may disposed the ID nodes in aregionally dispersed and distributed configuration of the sensor-basedID nodes having different ones of the sensor-based ID nodes disposed andintegrated into different ones of the respective regions of thedetection blanket.

As shown in FIG. 71, packages 1-4 are positioned on top of node-enableddetection blanket 70005 b and then covered with another detectionblanket—e.g., a flexible type of detection blanket (e.g., exemplarydetection blanket 70005 a). As noted above, exemplary detection blanket70005 a has integrated sensor-based ID nodes 71120 a-71120 d. But ratherthan being made of a rigid core material as blanket 70005 b (asexplained in more detail in FIG. 72), exemplary detection blanket 70005a allows for the detection blanket 70005 b to more flexibly cover orconform to items/objects around the blanket, such as packages 1-4. Forexample, detection blanket 70005 a may be selectively connected tomultiple attachment points (e.g., hooks, eyes, recessed anchors, and thelike) within the shipping container 24300 a to physically restrainmovement of packages 1-4 as shown in FIG. 71. In a further example,detection blanket 70005 a may be selectively connected to one or more ofsuch attachment points (e.g., hooks, eyes, recessed anchors, and thelike) within the shipping container 24300 a to at least partiallyphysically restrain movement of the detection blanket 70005 a itself asshown in FIG. 71 even though such attachment may not physically restrainmovement of any of packages 1-4.

As noted above, an exemplary detection blanket may be implemented, forexample, as a single solid panel, a group of multiple connected panels,or with flexible material (e.g., cargo net, webbing, braided net,reinforced tarp, and the like) that are integrated with one or more IDnodes (such as sensor-based ID nodes). FIG. 72 is a diagram illustratingdetails of an exemplary single solid rigid panel type of node-enableddetection blanket 70005 b in accordance with an embodiment of theinvention. As shown in FIG. 72, exemplary detection blanket 70005 b isreproduced with a close up sectional view illustrating how blanket 70005b has a rigid core 72000 with cushioning sheets 72005, 72010 attached toeither side of the rigid core sheet 7200. In this manner, exemplarydetection blanket 70005 b may function on the floor of shippingcontainer 24300 a (or as one of different rigid separators betweenpackages).

FIG. 73 is a diagram illustrating an exemplary node-enabled detectionblanket 70005 c having multiple interconnected panels in accordance withan embodiment of the invention. Referring now to FIG. 73, exemplarydetection blanket 70005 c is shown having multiple flexibly connectedpanels 73010, wherein one or more of the sensor-based ID nodes (such assensor-based ID nodes 73120 a-73120 d—similarly configured as ID nodes71120 a-71120 d described above) are integrated into a different one ofthe flexibly connected panels 73010 as part of the geographicallydisperse configuration. In a further embodiment, one or more of theflexibly connected panels of exemplary detection blanket 70005 b may nothave an integrated sensor-based ID node and, instead, may implement afire suppression panel having integrated fire suppression material thatis passively releasable from the fire suppression panel when the firesuppression panel is exposed to a threshold temperature. An example ofsuch a fire suppression panel is explained in more detail above as panel54000 used as part of a shipping container, but in these embodimentssuch a panel may be used as part of or as one of the flexibly connectedpanels of an exemplary detection blanket so as to have its interiorfacing surface melt due to high heat conditions near the panel (due toan environmental anomaly) and quickly release an amount of firesuppression material maintained behind the interior facing surface as aresult.

FIG. 74 is a diagram illustrating further details of an exemplaryflexible webbing type of node-enabled detection blanket 70005 d inaccordance with an embodiment of the invention. As shown in FIG. 74,exemplary detection blanket 70005 d is implemented with a webbing (e.g.,cargo net, braided webbing, and the like) where sensor-based ID nodes74120 a-74120 e (similarly configured as ID nodes 71120 a-71120 ddescribed above) are attached to or integrated into different respectiveparts of the webbing as part of the geographically disperseconfiguration. With such a type of detection blanket, an embodiment mayimplement the environmental sensor on at least one of the sensor-basedID nodes 74120 a-74120 e as a continuity sensor configured to generatesensor data indicative of a damaged status of the part of the webbingassociated with the particular sensor-based ID node. The sensor datagenerated by the continuity sensor may exceed the threshold conditionwhen the sensor data changes from a predetermined first state indicativeof no damage to that part of the webbing associated with thatsensor-based ID node to a second state indicating that part of thewebbing associated with that particular sensor-based ID node has broken(e.g., is burned in two, separated, or otherwise is no longer in onepiece). Such a continuity sensor may be implemented with a fuse-basedsensor reactive to heat, where a particular temperature causes the fusein the sensor to trip or open, triggering a change in state for thesensor data generated. As such, the second state indicates that the partof the webbing association with that particular sensor-based ID node hasbeen exposed to a predetermined temperature as the threshold conditionthat changes the fused-based sensor from the first state to the secondstate.

In another embodiment where one or more of sensor-based ID nodes 74120a-74120 e are integrated as part of the webbing, the webbing materialitself can serve as a type of node enclosure for a particular integratedsensor-based ID node. In more detail, one or more of sensor-based IDnodes 74120 a-74120 e may be disposed within a section of the webbingmaterial so as to be encompassed by the webbing material. Depending onthe material chosen for such webbing material, exposure to anenvironmental anomaly (e.g., fire, chemical, and the like) may damagethe webbing material proximate the integral sensor-based ID node so asto expose the components of the integral sensor-based ID node to theenvironmental anomaly. Thus, once the webbing based node enclosure hasgiven way, which exposes the otherwise enclosed ID node, the ID node maycease operation or may detect a particular environmental condition thatcrosses a threshold for indicating the environmental anomaly. And, asexplained above, should the enclosed ID node's sensor be implementedwith a continuity sensor, the enclosed ID node sensor may also detect aparticular state indicative of damage to the webbing due simply to thelack of enclosure protection from the webbing section that normallyencloses that ID node.

These different embodiments of exemplary detection blankets may deploy avariety of different types of sensors as well as a mix of differentsensors on a given detection blanket. For example, the environmentalsensor for one of the sensor-based ID nodes in an exemplary detectionblanket may be a temperature sensor while the environmental sensor foranother sensor-based ID node in the detection blanket may be abarometric pressure sensor. In another example, the environmental sensorfor one of the sensor-based ID nodes in an exemplary detection blanketmay have multiple sensor elements, such as a temperature sensor elementand a barometric pressure sensor element. In still another example, theenvironmental sensor for one of the sensor-based ID nodes in anexemplary detection blanket may be a temperature sensor while theenvironmental sensor for another of the sensor-based ID nodes in thedetection blanket may be a radiation sensor or a chemical sensor.

Examples of node-enabled detection blankets may also use particularsensors in a proactively layered failure configuration as part of suchan apparatus that may be used to detect an environmental anomaly. Forexample, an embodiment of a node-enabled detection blanket may have afirst group of the sensor-based ID nodes that cease to broadcast thesensor data generated by each of the first group of sensor-based IDnodes when the environmental sensor in each of the first group ofsensor-based ID nodes indicates a first temperature value exceeding afirst temperature threshold while a second group of sensor-based IDnodes in the detection blanket continue to broadcast the sensor datagenerated by each of the second group of the sensor-based ID nodes. Inmore detail, such a second group of sensor-based ID nodes in thedetection blanket may cease to broadcast the sensor data generated byeach of the second group of sensor-based ID nodes when the environmentalsensor in each of the second group of sensor-based ID nodes indicates asecond temperature value exceeding a second temperature threshold whilea third group of the sensor-based ID nodes in the detection blanketcontinue to broadcast the sensor data generated by each of the thirdgroup of the sensor-based ID nodes (where the first temperaturethreshold is lower than the second temperature threshold). In thismanner, the configuration of particular sensors and their designed incapacity to cease broadcasting once certain temperatures are reachedprovides the ability of a monitoring command node to quickly assess suchlayered failures built into such an exemplary detection blanket anddetect a particular environmental anomaly on such a monitored basiswithout regard to actual sensor data values.

FIG. 75 is a diagram illustrating another exemplary system for enhanceddetecting of an environmental anomaly relative to packages maintained ina shipping container using multiple node-enabled detection blanketsdisposed relative to different layers of the packages in accordance withan embodiment of the invention. Referring now to FIG. 75, exemplarysystem 75000 is shown similar to that shown with system 71000 in FIG.71, but system 75000 has shipping container 24300 a loaded with furtherpackages and deploys a different combination of node-enabled detectionblankets 70005 a, 70005 e. In more detail, shipping container 24300 a asshown in FIG. 75 now has packages 5-8 loaded on the floor of container24300 with exemplary node-enabled detection blanket 70005 e on top ofthose packages. Blanket 70005 e is shown in the example of FIG. 75 as aflexible material type of node-enabled detection blanket havingsensor-based ID nodes 75120 e-75120 h integrated as part of detectionblanket 70005 e. The same combination of packages 1-4 and node-enableddetection blanket 70005 a are shown on top of detection blanket 70005 ewith each of blankets 70005 a and 70005 selectively attached todifferent attachment points within shipping container 24300 a tophysically restrain the collective movement of packages 1-8. In afurther example illustrated in FIG. 75, detection blanket 70005 a may beselectively connected to one or more of such attachment points (e.g.,hooks, eyes, recessed anchors, and the like) within the shippingcontainer 24300 a to at least partially physically restrain movement ofthe detection blanket 70005 a itself as shown in FIG. 75 even thoughsuch attachment may not physically restrain movement of any of packages1-8.

In the context of the environment shown in FIG. 75 and explained abovewhere command node 1 may monitor signals from each of the node-enableddetection blankets 70005 a, 70005 e (as well as other ID nodes disposedwithin shipping container 24300 a, such as ID node 4 that is associatedwith package 4) and respond with notifications to further elements ofsystem 75000 (e.g., external transceiver 24150, fire suppression system25010), further system embodiments may be described as follows.

For example, an exemplary system for enhanced detecting of anenvironmental anomaly may include detection blanket 70005 a disposedwithin shipping container 24300 a and proximate to packages (such aspackages 1-4) within the shipping container. The system further includessensor-based ID nodes 70120 a-70120 d integrated as part of detectionblanket 70005 a in a geographically disperse configuration relative tothe detection blanket 70005 a. As described above, each of theintegrated sensor-based ID nodes 70120 a-70120 d have an ID nodeprocessor, an ID node memory coupled to the ID node processor, anenvironmental sensor, and an ID node wireless radio transceiver. The IDnode memory maintains at least an ID node monitoring program code (e.g.,code that is part of node control and management code 325) that, whenexecuting, controls the operation of the respective integrated ID nodeas part of this system. The environmental sensor (or sensors on the IDnode) are configured to generate sensor data related to an environmentalcondition adjacent the environmental sensor (such as sensor data ontemperature). The ID node wireless radio transceiver is operativelyresponsive to the ID node processor, and is configured to access thesensor data generated by the environmental sensor and broadcast thesensor data in response to a report command from the ID node processorwhen the ID node processor executes the ID node monitoring program code.

The system embodiment further includes command node 1 mounted on theshipping container 24300 a. As noted above, command node 1 has a commandnode processor, a command node memory, and a command node wirelesstransceiver. The command node memory operatively is coupled to thecommand node processor and maintains at least command node containermanagement program code (e.g., code that is part of CN control andmanagement code 26435). The command node wireless transceivercommunication interface is operatively responsive to the command nodeprocessor and is configured to communicate with each of the sensor-basedID nodes of the detection blanket and with the external transceiver. Insome embodiments, the command node wireless transceiver communicationinterface may be implemented with separate communication interfaces,where a first communication interface is operatively responsive to thecommand node processor and configured to communicate with each ofsensor-based ID nodes 70120 a-710120 d of the detection blanket 70005 aover a first wireless communication path, while a second communicationinterface is also operatively responsive to the command node processorand configured to communicate with at least external transceiver 24150(and with fire suppression system 25010 in some embodiments) using asecond wireless communications path distinct from the first wirelesscommunication path.

During operation of such a system embodiment, the command node processorof command node 1 is programmatically configured, when executing thecommand node container management program code, to be operative todetect the sensor data broadcasted from sensor-based ID nodes 70120a-70120 d of detection blanket 70005 a using the command node wirelesstransceiver communication interface; responsively identify theenvironmental anomaly for the shipping container 24300 a based uponvalues of the detected sensor data; generate an alert notificationrelated to the identified environmental anomaly for the shippingcontainer 24300 a; and cause the command node wireless transceivercommunication interface to transmit the alert notification to at leastexternal transceiver 24150 to initiate a mediation response related tothe identified environmental anomaly.

In more detail, the system embodiment may have the command nodeprocessor of command node 1 being further programmatically operative toidentify detection blanket 70005 a by communicating with at least one ofsensor-based ID nodes 70120 a-70120 d of detection blanket 70005. Thesensor data generated by ID nodes in a detection blanket may includeidentification information about the detection blanket associated with aparticular ID node in that blanket.

The system embodiment may also have the command node processor ofcommand node 1 be further programmatically configured to responsivelyidentify the environmental anomaly for shipping container 24300 a basedupon values of the detected sensor data by being further operative todetect the environmental anomaly for the shipping container when thedetected sensor data from at least one of sensor-based ID nodes 70120a-70120 d exceeds an environmental threshold condition. For example,command node 1 may detect such an environmental anomaly when: (a) thesensor data detected from a first of sensor-based ID nodes 70120 a-70120d in detection blanket 70005 a comprises a temperature value; (b) thesensor data detected from a second of the sensor-based ID nodes 70120a-70120 d in detection blanket 70005 a comprises an environmentalcondition value of one of a sensed barometric pressure level, a detectedradiation level, or a detected chemical (e.g., a chemical indicative ofa fire, explosive, CO, or CO₂); (c) the temperature value indicates theenvironmental condition adjacent the first of these ID nodes exceeds atemperature threshold condition; and (d) the environmental conditionvalue indicates the environmental condition adjacent the second of theseID nodes exceeds an environmental threshold condition associated withthe environmental sensor of that second ID node.

Such a system embodiment may detect various types of environmentalanomalies. For example, the detected environmental anomaly for shippingcontainer 24300 a may be a fire within shipping container 24300 a whencommand node 1 determines that, based upon the sensor data, (a) thetemperature value from the first of sensor-based ID nodes 70120 a-70120d in detection blanket 70005 a exceeds the temperature thresholdcondition; and (b) the environmental condition value as the sensedbarometric pressure level from the second of these sensor-based ID nodesexceeds a pressure threshold as the environmental threshold condition.In another example, the detected environmental anomaly for shippingcontainer 24300 a may be an explosion within shipping container 24300 awhen command node 1 determines that, based upon the sensor data, (a) thetemperature value from the first of the sensor-based ID nodes 70120a-70120 d in detection blanket 70005 a exceeds the temperature thresholdcondition; and (b) the environmental condition value as the sensedbarometric pressure level from the second of these sensor-based ID nodesis detected below a pressure threshold as the environmental thresholdcondition. In still another example, the detected environmental anomalyfor shipping container 24300 a may be an explosion within shippingcontainer 24300 a when command node 1 determines that, based upon thesensor data, (a) the temperature value from the first of thesensor-based ID nodes 70120 a-70120 d in detection blanket 70005 aexceeds the temperature threshold condition; and (b) the environmentalcondition value as the sensed barometric pressure level from the secondof these sensor-based ID nodes is detected to be dropping faster than apressure drop threshold as the environmental threshold condition. Inanother example, the detected environmental anomaly for shippingcontainer 24300 a may be a detected chemical fire within shippingcontainer 24300 a when command node 1 determines that, based upon thesensor data, (a) the temperature value from the first of thesensor-based ID nodes 70120 a-70120 d in detection blanket 70005 aexceeds the temperature threshold condition; and (b) the environmentalcondition value as the detected chemical from the second of thesesensor-based ID nodes matches a predetermined chemical profilemaintained by command node 1 in the command node memory (e.g., as partof profile data 430). In yet another example, detected environmentalanomaly for the shipping container may be a detected radiation leakwithin shipping container 24300 a when command node 1 determines that,based upon the sensor data, (a) the temperature value from the first ofthe sensor-based ID nodes 70120 a-70120 d in detection blanket 70005 aexceeds the temperature threshold condition; and (b) the environmentalcondition value as the detected radiation from the second of thesesensor-based ID nodes matches a predetermined radiation profilemaintained by command node 1 in the command node memory (e.g., as partof profile data 430).

Another exemplary system for enhanced detecting of an environmentalanomaly may involve similar system elements (e.g., detection blanket70005 a having integrated ID nodes 70120 a-70120 d, and command node 1),but have the command node alternatively configured via its programmingto monitor for unresponsive ones of ID nodes 70120 a-70120 d withindetection blanket 70005 a. In more detail, such a system embodiment mayhave the command node processor of command node 1 being programmaticallyconfigured, when executing the command node container management programcode, to be operative to identify detection blanket 70005 a byresponsively communicating with each of ID nodes 70120 a-70120 d ofdetection blanket 70005 a (without necessarily receiving sensor datafrom such nodes) and comparing the responsive ones of these ID nodeswith a blanket identification profile maintained by the command node inthe command node memory (e.g., part of profile data 430); monitor theadvertising messages broadcasted from ID nodes 70120 a-70120 d ofdetection blanket 70005 a using the command node wireless transceivercommunication interface to identify an unanticipated state of ceasedbroadcasting from any of these ID nodes; responsively identify theenvironmental anomaly for shipping container 24300 a when a number of IDnodes 70120 a-70120 d identified to be in the unanticipated state ofceased broadcasting exceeds a threshold setting maintained by commandnode 1; generate an alert notification related to the identifiedenvironmental anomaly for shipping container 24300 a; and cause thecommand node wireless transceiver communication interface to transmitthe alert notification to external transceiver 24150 to initiate amediation response related to the identified environmental anomaly.

As the monitoring by command node 1 in this system embodiment involvesmonitoring for ceased broadcasting status of particular ID nodes, afurther embodiment may have command node 1 monitoring to take advantageof a proactively layered failure configuration of the ID nodesintegrated into detection blanket 70005 a. For example and consistentwith the prior description of a proactively layered failureconfiguration of a detection blanket's integrated ID nodes, the ID nodes70120 a-70120 d integrated as part of detection blanket 70005 a mayinclude a first group and a second group, where the first group areintegrated ID nodes operative to cease broadcasting advertising messageswhen a temperature adjacent that first group exceeds a first temperaturethreshold while the second group are integrated ID nodes that continueto broadcast advertising messages at that first temperature threshold.In a further example, the second group of ID nodes may ceasebroadcasting when a temperature adjacent the second group of the IDnodes exceeds a second temperature threshold while a third group of theintegrated ID nodes continue to broadcast the advertising messages. Inthis example, the first temperature threshold is lower than the secondtemperature threshold. As such, the command node processor of commandnode 1 in the system may be further programmatically configured toresponsively identify the environmental anomaly as a first level anomalyfor shipping container 24300 a when command node 1 ceases to detect theadvertising messages from any of the first group of integrated ID nodesin detection blanket 70005 a, and may also responsively identify theenvironmental anomaly as a second level anomaly for shipping container24300 a when command node 1 ceases to detect the advertising messagesfrom any of the second group of integrated ID nodes in detection blanket70005 a.

A further exemplary system for enhanced detecting of an environmentalanomaly may involve similar system elements (e.g., detection blanket70005 a having integrated ID nodes 70120 a-70120 d, and command node 1),but also include a second detection blanket (e.g., detection blanket70005 e having integrated ID nodes 75120 e-75120 h) as part of thesystem. As such, the system includes a first detection blanket 70005 adisposed within shipping container 24300 a and proximate at least afirst group of the packages 1-4 within the shipping container, wheredetection blanket 70005 a has a first group of sensor-based ID nodes70120 a-70120 d integrated as part of the first detection blanket 70005a. Each of the first group of sensor-based ID nodes 70120 a-70120 d aredisposed as part of the first detection blanket 70005 a in a firstgeographically disperse configuration and include at least a firstenvironmental sensor configured to generate first detection blanketsensor data related to an environmental condition adjacent the firstenvironmental sensor and a first wireless radio transceiver configuredto broadcast the first detection blanket sensor data. The system alsoincludes a second detection blanket 70005 e disposed within shippingcontainer 24300 a and proximate at least a second group of the packages5-8 within shipping container 24300 a, where the second detectionblanket 70005 e has a second group of sensor-based ID nodes 75120e-75120 h integrated as part of the second detection blanket 70005 e.Each of the second group of sensor-based ID nodes 75120 e-75120 h aredisposed as part of the second detection blanket 70005 e in a secondgeographically disperse configuration and include at least a secondenvironmental sensor configured to generate second detection blanketsensor data related to an environmental condition adjacent the secondenvironmental sensor and a second wireless radio transceiver configuredto broadcast the second detection blanket sensor data.

The system's command node, command node 1 on shipping container 24300 aas described above, includes at least a command node processor, acommand node memory operatively coupled to the command node processor(maintaining at least command node container management program code(e.g., code that may be part of CN control and management code 26425)),and a command node wireless transceiver communication interface. Thecommand node wireless transceiver communication interface (which may beimplemented as a single transceiver interface or dual transceivers) isoperatively responsive to the command node processor, and configured tocommunicate with each of the sensor-based ID nodes of both detectionblankets 70005 a, 70005 e as well as with the external transceiver 24150(and with fire suppression system 25010 in some embodiments).

During operation of the multiple detection blanket system embodiment,the command node processor of command node 1 is programmaticallyconfigured, when executing the command node container management programcode, to be operative to detect a first signal from one of the firstgroup of sensor-based ID nodes (e.g., ID nodes 70120 a-70120 d) in thefirst detection blanket 70005 a to register the first detection blanket70005 a as a first monitoring blanket within the shipping container24300 a, and detect a second signal from one of the second group ofsensor-based ID nodes (e.g., ID nodes 75120 e-75120 h) in the seconddetection blanket 70005 e to register the second detection blanket 70005e as a second monitoring blanket within the shipping container. Commandnode 1 is further programmatically configured to be operative to thendetect the first detection blanket sensor data broadcasted from thefirst group of the sensor-based ID nodes in the first detection blanketusing the command node wireless transceiver communication interface;detect the second detection blanket sensor data broadcasted from thesecond group of the sensor-based ID nodes in the first detection blanketusing the command node wireless transceiver communication interface;responsively identify the environmental anomaly for the shippingcontainer based upon values of at least one of the detected firstdetection blanket sensor data and the detected second detection blanketsensor data; generate an alert notification related to the identifiedenvironmental anomaly for the shipping container; and cause the commandnode wireless transceiver communication interface to transmit the alertnotification to external transceiver 24150 to initiate a mediationresponse related to the identified environmental anomaly.

As part of this multiple detection blanket system, the first detectionblanket may be disposed below or above the first group of the packages.Likewise, embodiments may have the second detection blanket beingdisposed above or below the second group of the packages.

An embodiment of such a multiple detection blanket system may have oneof the detection blankets having at least a first rigid sheet withinwhich the first group of sensor-based ID nodes is integrated in thefirst geographically disperse configuration, while the second detectionblanket has at least a second rigid sheet within which the second groupof sensor-based ID nodes is integrated in the second geographicallydisperse configuration.

Alternatively, the first and second blankets may be made of flexiblecargo webbing. In more detail, an embodiment may have the firstdetection blanket being implemented with cargo webbing, where each ofthe first group of sensor-based ID nodes are integrated into a differentpart of that cargo webbing as part of the first geographically disperseconfiguration. Likewise, the second detection blanket may also beimplemented cargo webbing, where each of the second group ofsensor-based ID nodes are integrated into a different part of that cargowebbing as part of the second geographically disperse configuration. Inmore detail when the detection blankets are implemented with cargonetting, an environment sensor on the sensor-based ID nodes integratedas part of such detection blankets may be implemented as a fuse-basedcontinuity sensor that is reactive to heat and configured to generatesensor data indicative of a damaged status of that part of the cargowebbing associated with respective integrated sensor-based ID nodes.

In still another embodiment, one detection blanket may have a rigid corestructure while the other has a flexible webbing structure. In moredetail, the first detection blanket may be implemented with a rigidsheet (or multiple rigid panels) within which the first group ofsensor-based ID nodes is integrated in the first geographically disperseconfiguration, while the second detection blanket may be implementedwith cargo webbing within which second group of sensor-based ID nodes isintegrated as part of the second geographically disperse configuration.

In a further embodiment of such a multiple detection blanket system, thecommand node processor of command node 1 may be further programmaticallyoperative to identify the first detection blanket and the seconddetection blanket by communicating with at least one within the firstgroup of sensor-based ID nodes and with at least one within the secondgroup of sensor-based ID nodes.

While the exemplary shipping container 24300 a described with respect tovarious embodiments involving exemplary detection blankets have beencontainers having a base, walls, and a top/lid that enclose thecontainer and define an interior storage area within the shippingcontainer, further embodiments of exemplary shipping containers may alsoinclude a pallet-based container having a securing structure attached tothe pallet to at least temporarily hold what is supported on the palletin place. FIGS. 76A-76C are a series of diagrams illustrating anexemplary shipping container implemented with an exemplary base palletand an exemplary node-enabled detection blanket attached to the basepallet along with additional features that may be deployed as part ofthe exemplary node-enabled detection blanket in accordance with anembodiment of the invention.

FIG. 76A is a diagram illustrating an exemplary shipping containerhaving an exemplary base pallet with a node-enabled detection blanketattached to the base pallet as a type of securing structure thatencloses packages maintained on the base pallet in accordance with anembodiment of the invention. Referring now to FIG. 76A, those skilled inthat art will appreciate that exemplary pallet-based container 76000 isillustrated supporting a group of packages 70400. Exemplary node-enableddetection blanket 70005 shown in FIG. 76A is able to function as part ofshipping container 76000 as it covers packages 70400 and may attach viatie-downs 70015 to different attachment points 76010 on pallet 76005.While not shown in FIG. 76A as it may be hidden within or mounted topallet 76005 (or within a package 70400), shipping container 76000 mayhave an exemplary command node (such as command node 1 as explained inthe various embodiments above) that may monitor integrated ID nodeswithin detection blanket 70005, detect an environment anomaly related toshipping container 76000 similar to that described in embodiments above,and report relevant alert notifications that may initiate a mediationresponse by other devices (e.g., external transceiver 24150 or firesuppression system 25010) similar to that described in the variousembodiments describe above.

FIGS. 76B and 76C each provide further details related to variousembodiments of exemplary node-enabled detection blanket 70005 asimplemented with webbing material. In more detail and referring now toFIG. 76B, a magnified view of part of exemplary node-enabled detectionblanket 70005 made from flexible webbing 76200, which may have one ormore of the blanket's sensor-based ID nodes disposed on or within thewebbing 76200. As shown in FIG. 76B, a connection point 76300 (e.g., aclasp, clip, connector, snap, and the like) is shown attached to anattachment point 76010 (e.g., a hook, eye, recessed anchor, and thelike) on the shipping container's base via tie down straps 70015 securedto part of the base of the container (e.g., base pallet 76005).Exemplary connection point 76300, in a particular embodiment, may be aconnector having an integrated one of the sensor-based ID nodes in theblanket 70005. As such, the environmental sensor on that sensor-based IDnode integrated into connection point 76300 may, for example, beimplemented as a continuity sensor (e.g., RF sensor, NFC sensor, and thelike) configured to generate sensor data indicative of an attachmentstatus of the connection point 76300 to an attachment point on theshipping container (attachment point 76010 on the shipping container'sbase having tie down straps 70015 that may be attached to connectionpoint 76300). The attachment status may then be reported as a type ofsensor data, and may be used by a command node as part of monitoring forand detecting an environmental anomaly as the state of such a monitoredattachment may help indicate whether a fire or explosion has occurred.

In FIG. 76C, an alternative embodiment of such exemplary flexiblewebbing 76200 is illustrated with a magnified portion of exemplarydetection blanket 70005 shown made from multiple connectable webbingsections 76205 a that make up a connected webbing 76200 a. Eachconnectable webbing section 76205 a, in this example, is shown havingconnectors on ends of the section (e.g., a first connector 76210 a toconnect to another connector 76210 b on another webbing section). Suchconnectors may be implemented with single or multiple connectorsdepending on the webbing section configurations being attached to eachother to form the connected webbing. An embodiment may have one or moresensors integrated into such connectors that are coupled to an ID nodedisposed on the particular webbing section having such connectors. Suchsensors may, for example, be temperature or pressure sensors thatgenerate environmental sensor data about the surrounding environmentnear the connectors. However, in another example, such sensors may beimplemented with a continuity sensor configured to generate sensor dataindicative of an attachment status of the sensor's connector to anotherwebbing section's connector. The attachment status in this situation maythen be reported as a type of sensor data, and may be used by a commandnode as part of monitoring for and detecting an environmental anomaly asthe state of such a monitored attachment may help indicate whether afire or explosion has occurred. Such attachment status, as sensor data,may be monitored to detect a change in connection of the detectionblanket's webbing, which may be indicative of an environmental anomaly(e.g., a fire burned through the webbing section or the connection nolonger exists due to the fire). Further, such a change of attachmentstatus may be used by the command node in combination of other sensordata (e.g., an increase in temp, a change in pressure that may match apressure profile) to provide further detailed sensor data with which thecommand node may use to not only detect the environmental anomaly, butto adaptive generate an alert notification and fashion the appropriateinformation as part of the notification to initiate an appropriatemediation response as discussed in embodiments herein.

A further example may have wiring run through sections of the webbing soas to be connected to form a network of wiring that may be centrallymonitored or sensed with a single ID node. In this way, any break of thewebbing may be sensed by the ID node and reflected in the sensor datagenerated by that ID node. Further still, if the wiring is power wiring,any break may cause the ID node to cease broadcasting when anticipatedto be broadcasting and, as such, any such break may be detected asrelevant to detecting an environmental anomaly as well as what anysensor data may substantively indicate.

Still further embodiments may deploy one or more detection blanketswithin a shipping container and have a command node perform multi-modetriggering to detect an environmental anomaly (e.g., monitor both sensordata values as compared to sensor threshold as well as the number ofunresponsive integrated ID nodes that are expected and anticipated to bebroadcasting under normal conditions). More embodiments may combine theuse of attachment status sensor data as part of the monitoring ofsignals and signal activity to detect an environmental anomaly.

Adaptive and Prioritized Node Reporting

In various embodiments described above, a command node (as part of asystem that monitors different ID nodes for sensor data being generatedby such ID nodes for purposes of detecting an environmental anomaly) isdescribed as having the ability to selectively set and adjust rates forobtaining sensor data from the sensor-based ID nodes being monitored.Further embodiments expand on these principles in varying messagingrates on what is reported from a selective one or more of the ID nodes,as well as modifying what is monitored (e.g., which ID nodes aremonitored, what type of data should be considered when monitoring, andthe like) as a way of prioritizing or selectively prioritizing what maybe considered in an adaptive manner as the command node continuesmonitoring to detect the environmental anomaly. As such, these furtherembodiments involve the command node refining how it interacts with thesensor-based ID nodes that generate the sensor data as well as modifyingwhat is particularly monitored out of the potential available sensordata from the ID nodes so as to improve the focus and speed of detectingan environmental anomaly by dispensing with processing overhead withless relevant sensor data as the command node hones in on making thedetermination that an environmental anomaly exists within the shippingcontainer and rapidly responding to that determination by initiating amediation response.

FIG. 77 is a flow diagram illustrating an exemplary adaptive method formonitoring a shipping container for an environmental anomaly using awireless node network as a command node refines monitoring whendetecting the environmental anomaly in accordance with an embodiment ofthe invention. Such an exemplary method 7700 as described on FIG. 77generally includes multiple sensor-based ID nodes (e.g., ID nodes 1-7shown in FIG. 37A) disposed within the shipping container (e.g.,shipping container 24300 a) and a command node (e.g., command node24160) associated with the shipping container and operative tocommunicate with each of the sensor-based ID nodes and an externaltransceiver (e.g., external transceiver 24150) associated with a transitvehicle (e.g., transit vehicle 24200) having at least temporary custodyof the shipping container. The sensor-based ID nodes used as part ofmethod 7700 each have at least one environmental sensor. Thesesensor-based ID nodes may have one or more being disposed on orintegrated as part of the shipping container (e.g., ID nodes 4-7 shownin FIG. 37A being disposed on or integrated as part of a wall withinshipping container 24300 a) or associated with an object beingtransported within the shipping container (e.g., ID nodes 1-3 beingaffixed or attached to packages 1-3 or disposed within packages 1-3being transported within shipping container 24300 a). The command nodeused as part of method 7700 may be implemented, for example, as acontainer node integrated as part of the shipping container, mounted tothe shipping container, or a master node associated with the shippingcontainer and implemented separately from the shipping container whileattached to the shipping container. Further, the transit vehicle used aspart of method 6900 may be, for example, an airplane, a railwayconveyance, a maritime vessel, or a roadway conveyance.

Referring now to FIG. 77, exemplary method 7700 begins at step 7705 withthe environmental sensor on each of the ID nodes generating sensor datarelated to an environmental condition proximate the respective ID nodeas disposed within the shipping container. For example, each of ID nodes1-7 as shown in FIG. 37A have sensors (e.g., temperature sensors,pressure sensors, chemical sensors, radiation sensors, or the like) thatgenerate sensor data reflective of the environmental condition next toeach of ID nodes 1-7.

At step 7710, method 7700 continues with each of the sensor-based IDnodes periodically broadcasting the sensor data generated by each of theID nodes over time. For example, ID nodes 1-7 shown in FIG. 37A will be,over time, broadcasting their respectively generated sensor data viaadvertising signals transmitted over the wireless radio transceiver ineach of ID nodes 1-7.

At step 7715, method 7700 continues with the command node monitoring afirst group of the sensor data broadcast from each of the ID nodes. Thisis done over a first time period to detect an initial environmentalthreshold condition related to the shipping container. In the exampleillustrated with the components shown on FIG. 37A, exemplary commandnode 24160 may be programmatically configured (via code executing on theprocessor of command node 24160) to monitor the sensor data broadcast byID nodes 1-7 over a first time period. During that time period, commandnode 24160 may compare the sensor data from each of ID nodes 1-7 againstan initial environmental threshold setting (e.g., a first stagetemperature value indicative of a possible fire or other abnormal heatgenerating event, such as a dangerous chemical reaction, within shippingcontainer 24300 a).

At step 7720, if the command node fails to detect an initialenvironmental threshold condition related to the shipping container, themethod 7700 proceeds back to step 7715 for further monitoring. However,if the command node detects an initial environmental threshold conditionrelated to the shipping container as part of step 7720, method 7700proceeds directly to step 7725.

At step 7725, method 7700 continues with the command node monitoring asubsequent group of the sensor data broadcast from each of the ID nodesover a second time period under a modified monitoring parameter in aneffort to detect a secondary environmental threshold condition relatedto the shipping container as the environmental anomaly. In one example,step 7725 may have the modified monitoring parameter defining which ofthe ID nodes to consider when detecting the secondary environmentalthreshold condition. In this way, the command node may refine which IDnodes are prioritized when monitoring to detect the environmentalanomaly. In more detail, when each of the ID nodes is associated withone of a plurality of packages, the modified monitoring parameter maydefine which of the ID nodes to consider when detecting the secondaryenvironmental threshold condition based upon a type of material withinthe packages as associated with a respective one of the ID nodesaccording to shipping information maintained by the command node. Suchshipping information may identify what is in the particular packageassociated with a given ID node, the type of material within thatpackage, and whether that material may be designated as hazardous,flammable, combustible or have another designation that may cause thecommand node to consider prioritizing monitoring of that particular IDnode's sensor data relevant to such material.

In another example of step 7725, the modified monitoring parameter maydefine one or more types of the sensor data (e.g., temperature sensordata, pressure sensor data, chemical sensor data, and radiation sensordata) being broadcast from the ID nodes to consider when detecting thesecondary environmental threshold condition. For instance, withreference to FIG. 37A, command node 24160 may refine what is to bemonitored when detecting the secondary environmental threshold condition(e.g., an environmental condition that is indicative of theenvironmental anomaly) with a modified monitoring parameter that limitsthe type of sensor data considered by command node 24160 as part of step7725 to just temperature data, and ignore sensor data of other typescoming from the ID nodes generating sensor data. Which type of sensordata to focus on at step 7725 may also depend upon what, if any, type ofmaterial is associated with the ID nodes and is being transported withinthe shipping container 24300 a.

In still another example of step 7725, the step of monitoring thesubsequent group of the sensor data over the second time period underthe modified monitoring parameter may have the command node instructingeach of the ID nodes to change a messaging rate used to regulate howoften the generated sensor data is broadcast during the second timeperiod. This may increase or decrease the messaging rate to use duringthe second time period. In more detail, a further example may instruct afirst group of the ID nodes to increase the messaging rate from adefault messaging rate used during the first time period to a highersecondary messaging rate used during the second time period, and thenmonitoring the subsequent group of the sensor data broadcast from onlythe first group of the ID nodes over the second time period to detectthe secondary environmental threshold condition related to the shippingcontainer as the environmental anomaly. In this way, the command node isable to adapt by selectively choosing to prioritize sensor data comingfrom just that group of ID nodes and to make the sensor data coming fromthat group of ID nodes come quicker so that the command node may betterand more quickly detect the environmental anomaly so as to enhance howthe command node responds in a timely manner to initiate a mediationresponse.

At step 7730, method 7700 has the command node determining if it hasdetected the secondary environmental threshold condition related to theshipping container. If not, step 7730 proceeds back to step 7725 forcontinued monitoring. But if so, step 7730 has method 7700 proceedingdirectly to step 7735 where the command node generates an alertnotification related to the environmental anomaly for the shippingcontainer in response to detecting the secondary environmental thresholdcondition.

At step 7740, method 7700 continues with the command node transmittingthe alert notification to the external transceiver (e.g., externaltransceiver 24150 or a transceiver interface in fire suppression system25010) to initiate a mediation response related to the environmentalanomaly. The mediation response related to the environmental anomalymay, for example, cause a fire suppression system (e.g., firesuppression system 25010) to dispense fire suppressant material into theshipping container; cause the generation of a prompted messagerequesting an inspection of the shipping container (e.g., on a displayof external transceiver 24150 disposed in a logistics support area ofthe transit vehicle 24200); or cause the generation of a promptedmessage requesting the transit vehicle alter course as a result of theenvironmental anomaly (e.g., on a display of external transceiverdisposed in the cockpit of the transit vehicle 24200).

Those skilled in the art will appreciate that method 7700 as disclosedand explained above in various embodiments may be implemented using anexemplary adaptive monitoring system for detecting an environmentalanomaly in a shipping container such as that explained above withreference to FIG. 37A and its exemplary elements. Such an embodiment ofthis exemplary adaptive monitoring system, as explained above relativeto operations according to method 7700 and with elements from FIG. 37A,may use at least multiple sensor-based ID nodes disposed within theshipping container (e.g., ID nodes 1-7 shown in FIG. 37A) running one ormore ID node monitoring program code as part of node control andmanagement code 325 to control operations of the ID nodes to generateand broadcast ID node sensor data, as well as a command node mounted tothe shipping container (e.g., command node 24160 shown in FIG. 37A)running one or more parts of CN control & management code 26425 (e.g.,the command node container management program code that is part ofcommand node control and management code 26425) to control theoperations of the command node as part of adaptively monitoring ashipping container for an environmental anomaly. Such code may be storedon a non-transitory computer-readable medium, such as memory storage26415 on command node 24160 of FIG. 37A (which is an embodiment ofexemplary command node 26000) and memory storage 315 on sensor-based IDnodes 1-7 of FIG. 37A (embodiments of exemplary ID node 120 a). Thus,when executing such code, the ID nodes and the command node may beoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 7700 and variations of that method.

Command Node Deployed with a Package

Several embodiments described above include an exemplary command nodethat is mounted to or part of a shipping container that maintainsmultiple packages as it is transported on a transit vehicle. Examples ofsuch a “shipping container command node” include exemplary command node26000 as described with reference to FIG. 26 as well as exemplarycommand node 24160 described in the various examples and embodimentsabove. However, a further embodiment of an exemplary command node (e.g.,command node 26000, which may have its own sensors 26465) may beimplemented as an exemplary package command node. In general, anexemplary package command node is disposed with a shipment package(e.g., a package to be transported within a shipping container). Such anexemplary command node may have a node enclosure or housing that may belocated separately within the shipment package to travel with theshipment package as the shipment package is transported within theshipping container. The exemplary package command node may be disposedwithin the shipment package, attached (permanently or temporarily) tothe shipment package, or be integrated as part of the shipment package.As such, the exemplary package command node may monitor surrounding IDnodes (e.g., sensor-based ID nodes that generate sensor data reflectingenvironmental conditions relative to their respective location in theshipping container, as the nodes and/or sensor data may be verified orvalidated to be trusted data or sensor data from trusted sensors) andtake appropriate mediation action itself to directly initiate suchmediation responses or notify the shipping container command node thatmay be responsible for initiating such mediation responses.

Indeed, some embodiments of an exemplary package command node may bedeployed as a type of nested command node. For example, an exemplarypackage command node may be disposed with a large shipment package(e.g., palletized group of objects or packages) where another packagecommand node may be deployed within or as part of further componentswithin that large shipment package. In this way, some embodiments mayhave a system of multiple package command nodes that may be nested inlayers of a wireless node network where a lower level package commandnode may monitor and report on any detected anomaly it detects relativeto a subset of ID nodes within the shipping container. Such a lowerlevel package command node may report such detections through alerts upto the next level package command node, which may then report the sameup through a chain of network levels (depending on the implementation ofsuch a system) to the shipping container command node.

As such, the deployment of a package command node as part of a systemfor detecting an environmental anomaly relative to a shipping containerallows for further detailed monitoring on a distributed basis (e.g.,where the package command node or nodes handle the primary monitoringoperations relative to selective portions of the available ID nodeswithin the shipping container and offload the shipping container commandnode either temporarily or as a normal mode of environmental anomalydetection operation) while the shipping container command node monitorsthe different package container nodes and coordinates/initiates anappropriate mediation response via interaction with devices outside theshipping container (e.g., transceivers that interact with the transitvehicle's crew or transceivers that are part of an onboard firesuppression system).

FIG. 78 is a diagram illustrating an exemplary system for detecting anenvironmental anomaly related to a shipment package for transport withina shipping container on a transit vehicle having an external transceiverwhere the system includes an exemplary package command node inaccordance with an embodiment of the invention. Referring now to FIG.78, exemplary system 78000 is shown with similar components as system67000 in FIG. 67 (e.g., transit vehicle 24200, remote server 24100,network 24015, external transceiver 24150, onboard fire suppressionsystem 25010, and shipping container 24300 a), but FIG. 78 illustratesthe exemplary shipping container 24300 a without a shipping containercommand node (such as command node 1 shown in FIG. 67) but includes anexemplary package command node (e.g., package command node 78160 alsoreferenced as CN-P) and sensor-based ID nodes 1-4 shown disposed indifferent locations within the container 24300 a.

In more detail, sensor-based ID node 1 is shown in FIG. 78 as beingassociated with (e.g., attached to or disposed within) package 1 (alsoreferenced as package 24400 a) within shipping container 24300 a.Sensor-based ID node 2 is shown in FIG. 78 being disposed on the bottomfloor of shipping container 24300 a (sitting freely or attached).Sensor-based ID node 3 is shown in FIG. 78 as integrated as part of thecontainer 24300 a on a wall of the container, and sensor-based ID node 4is shown in FIG. 78 as attached to another wall of container 24300 a. Asimplementations of an exemplary ID node 120 a having one or more sensors360, each of sensor-based ID nodes 1-4 shown in FIG. 78 has an ID nodeprocessor, an environmental sensor, and a wireless radio transceiver(which may be implemented in hardware, in a combination ofhardware/software/or as a software defined radio (SDR)). Theenvironmental sensor in each ID node is coupled to the ID node processorand generates sensor data related to an environmental conditionproximate, nearby, or otherwise next to the respective sensor-based IDnode within the shipping container. The wireless radio transceiver isalso coupled to the ID node processor and operative to broadcast signalsthat include the sensor data (in additional to a validation record usedto confirm the sensor data broadcast as part of the signal is from thatparticular ID node) in response to a command from the ID node'sprocessor. As such, each of the sensor-based ID nodes 1-4 shown in FIG.78 generate sensor data from and about the environment proximate,nearby, next to, or otherwise at their respective locations withinshipping container 24300 a.

Exemplary package command node 78160 (CN-P) illustrated in FIG. 78 maybe implemented similarly to that explained above relative to exemplarycommand node 26000. For example, exemplary package command node 78160 isenclosed in a housing that is disposed with package 2 (as an exemplaryshipment package). As such, exemplary package command node 78160 may bedeposited within package 2, attached to either the inside or outside ofpackage 2, or placed within a pouch or other holder that is attached topackage 2. Similar to exemplary command node 26000, exemplary packagecommand node 78160 has at least a command node processor coupled to oneor more wireless transceiver-based communications interfaces as well asa command node memory. In one embodiment, the package command node'scommunications interface may be operative to communicate withsensor-based ID nodes 1-4 as well as externally disposed components,such as external transceiver 24150 and/or fire suppression system 25010located outside shipping container 24300 a. However in anotherembodiment with multiple communication interfaces, a first communicationinterface on the package command node may be operative to communicatewith each of sensor-based ID nodes 1-4 using a wireless communicationformat compatible with the wireless radio transceiver on each ofsensor-based ID nodes 1-4, while a second communication interface isoperative to communicate with the external transceiver 24150 associatedwith the transit vehicle 24200 using a second wireless communicationformat compatible with the external transceiver (as well as otherpackage command nodes that may be disposed in shipping container 24300a, or other transceivers on the transit vehicle 24200 outside ofcontainer 24300 a, or in further nested package command nodes withinpackage 2 (not shown)). Those skilled in the art will also appreciateexemplary package command node 78160 may be implemented as a master node(e.g., exemplary master node 110 a that may include its own sensors aswell as location circuitry that enables the master node to self-locate)or a container node that may not have location circuitry. Further,exemplary package command node 78160 may be integrated as part ofpackage 2 or be implemented separately (as a separate device) butremovably mounted to package 2.

The command node memory on package command node 78160 as shown in theembodiment illustrated in FIG. 78 may store and maintain at leastcommand node container management program code that has program codegoverning operations on package command node 78160 when detecting andresponding to environmental anomalies (e.g., package command nodeenvironmental detection program code that is part of command nodecontrol and management code 26425 on the memory of package command node78160). While not shown in FIG. 78, those skilled in the art willappreciate the package command node 78160 may also maintain securitycredentials (such as security credentials 67435 shown in FIG. 67relative to memory in command node 1) specific to one or more ofsensor-based ID nodes 1-4 that are to be trusted (e.g., a type ofsecurity data 435 explained generally above).

In operation and as part of an apparatus working in an embodiment ofsystem 78000 (e.g., package command node 78160 shown in FIG. 78), theprocessor of package command node 78160 is programmatically configuredvia its onboard executing programming (e.g., the package command nodeenvironmental detection program code that is part of command nodecontrol and management code 26425) to be operative to detect the sensordata broadcasted from the sensor-based ID nodes 1-4 using the commandnode wireless transceiver communication interface; responsively identifythe environmental anomaly for the shipping container 24300 a when thedetected sensor data from the sensor-based ID nodes 1-4 indicates anenvironmental condition that exceeds an environmental threshold;generate an alert notification related to the environmental anomaly forthe shipping container 24300 a in response to identifying theenvironmental anomaly for the shipping container 24300 a; and cause thecommand node wireless transceiver communication interface to transmitthe alert notification to the external transceiver to initiate amediation response related to the environmental anomaly.

Similar to exemplary command node 26000 (which has onboard sensors26465), an embodiment of package command node 78160 may include at leastone environmental sensor disposed with package 2 and operatively coupledto the command node processor of package command node 78160. Such anenvironmental sensor is operative to generate shipment package sensordata related to environmental conditions in or on package 2. As such,the command node processor of package command node 78160 may beprogrammatically configured to be operative to responsively identify theenvironmental anomaly for shipping container 24300 a by being furtherprogrammatically configured to responsively identify the environmentalanomaly for shipping container 24300 a when at least one of the detectedsensor data (i.e., the detected sensor data from the sensor-based IDnodes 1-4 and the detected shipment package sensor data from the packagecommand node's own sensor(s)) indicates the environmental conditionexceeds the environmental threshold.

In more detail, an embodiment of exemplary package command node 78160may have its command node processor programmatically configured to beoperative to responsively identify the environmental anomaly for theshipping container by being further programmatically configured toresponsively identify the environmental anomaly for the shippingcontainer when at least one of (a) the detected sensor data from thesensor-based ID nodes 1-4 indicates the environmental condition exceedsthe environmental threshold, and (b) when the detected sensor data fromthe sensor-based ID nodes 1-4 does not include the sensor data from atleast a threshold number of the sensor-based ID nodes 1-4. For example,the command node memory on package command node 78160 may maintaincontext data (e.g., part of context data 26560) identifying theparticular ones of sensor-based ID nodes 1-4 anticipated to bebroadcasting. As such, the command node processor of package commandnode 78160 may responsively identify the environmental anomaly forshipping container 24300 a by being further programmatically configuredto responsively identify the environmental anomaly for the shippingcontainer when at least one of (a) the detected sensor data from thesensor-based ID nodes 1-4 indicates the environmental condition exceedsthe environmental threshold, and (b) when the detected sensor data fromthose of sensor-based ID nodes 1-4 anticipated to be broadcastingaccording to the context data does not include sensor data from at leasta threshold number of those sensor-based ID nodes anticipated to bebroadcasting. Such context data that may identify those of sensor-basedID nodes anticipated to be broadcasting may have been received bypackage command node 78160 from external transceiver 24150 (which mayhave received such context data from remote control center server24100). As the server 24100 may the device managing the different nodeelements of system 78000, server 24100 may track which ID nodes (orother nodes) are anticipated to be broadcasting and when. Suchinformation may be provided as context information to other nodeelements of the network (such as external transceiver 24150 and packagecommand node 78160).

While package command node 78160 transmits the alert notification to theexternal transceiver to initiate a mediation response related to theenvironmental anomaly, such a mediation response may come in differentforms. For example, the mediation response initiated with thetransmitted alert notification may be implemented as an instruction toactivate a triggered fire suppression system on the transit vehicle(e.g., fire suppression system 25010) and in communication with externaltransceiver 24150. In another example, the mediation response initiatedwith the transmitted alert notification may be implemented as aninstruction to generate a prompted request to change course of thetransit vehicle from an existing travel path of the transit vehicle, oran instruction to generate a prompted request to investigate theshipping container.

Package command node 78160 may also, as part of identifying theenvironmental anomaly, verify or validate what ID node is providing thesensor data to avoid errors or spoofing ID nodes from providinginaccurate or unreliable sensor data. For example, command node memoryon package command node 78160 may maintain security credentialsassociated with trusted sensors for use with environmental anomalydetection. As such, the command node processor of package command node78160 may responsively identify the environmental anomaly for theshipping container by being further programmatically configured toidentify which of the sensor-based ID nodes 1-4 maintained withinshipping container 24300 a is one of the trusted sensors disposed withinthe shipping container based the security credentials. The identifiedones of sensor-based ID nodes 1-4 are then considered being confirmedsensor-based ID nodes. As such, the command node processor of packagecommand node 78160 may then monitor, via the command node wirelesstransceiver communication interface, only the confirmed ones ofsensor-based ID nodes 1-4 for sensor data broadcast from each of theconfirmed sensor-based ID nodes (while disregarding any sensor databroadcast from those of sensor-based ID nodes 1-4 not identified asbeing confirmed sensor-based ID nodes); and identify the environmentalanomaly for shipping container 24300 a when the monitored sensor databroadcast from each of the confirmed sensor-based ID nodes indicates anenvironmental condition that exceeds the environmental threshold.

Package command node 78160 may, as part of identifying the environmentalanomaly, verify or validate the sensor data itself to better ensure thesensor data is to be trusted and relied upon for any environmentalanomaly detection and responsive actions. For example, the command nodeprocessor of package command node 78160 may be further programmaticallyconfigured to be operative to validate the sensor data broadcast fromeach of sensor-based ID nodes 1-4 upon receiving the sensor data. Assuch, the command node processor of package command node 78160 may beprogrammatically operative to responsively identify the environmentalanomaly for shipping container 24300 a by being further programmaticallyconfigured to detect the environmental anomaly for shipping container24300 a when the sensor data validated by the package command node 78160indicates the environmental condition that exceeds the environmentalthreshold. In more detail, the command node processor of package commandnode 78160 may validate the sensor data by being furtherprogrammatically configured to determine which of the sensor datareceived by the command node processor during monitoring is valid byassessing a validation record within each of the received sensor databroadcast from each of sensor-based ID nodes 1-4 without requiring thecommand node processor to cause the command node wireless transceiver totransmit a validation request to each of sensor-based ID nodes 1-4.

A further embodiment illustrated in FIG. 78 includes a system embodimentthat deploys package command node 78160 with package 2 as explainedabove (including each variation and further detailed features andoperational capabilities) as well as each of sensor-based ID nodes 1-4as they generate sensor data and interact with package command node78160 as described above. In other words, the apparatus of exemplarypackage command node 78160 (as described generally and in more detail inthe various embodiments above) may be used as an element, in combinationwith each of sensor-based ID nodes 1-4, in a system embodiment thatdetects an environmental anomaly related to a shipment container on atransit vehicle.

Still further embodiments involve a similar system of components (e.g.,package command node 78160 and sensor-based ID nodes 1-4 as shown inFIG. 78) with the addition of a shipping container command node at anetwork layer above the package command node 78160. FIGS. 79A-79C arediagrams illustrating an exemplary system for detecting an environmentalanomaly related to a shipment package for transport within a shippingcontainer on a transit vehicle having an external transceiver where thesystem includes an exemplary package command node 78160 that interactsand works with an exemplary shipping container command node (e.g.,command node 1 as generally explained in embodiments above) inaccordance with an embodiment of the invention. Referring now to FIG.79A, exemplary system 79000 is shown with similar components as system67000 in FIG. 67 (e.g., transit vehicle 24200, remote server 24100,network 24015, external transceiver 24150, onboard fire suppressionsystem 25010, and shipping container 24300 a), but FIG. 79A illustratesthe exemplary shipping container 24300 a including exemplary shippingcontainer command node 1 mounted to shipping container 24300 a as wellas exemplary package command node 78160 (also referenced as CN-P) andsensor-based ID nodes 1-4 shown disposed in different locations withinthe container 24300 a. As shown in FIG. 79A, each sensor-based ID nodes1-4 generate sensor data from different parts of shipping container24300 a as explained above. Package command node 78160 is similarlydisposed as explained above with a package command node housing disposedwith the shipment package (package 2), a package command node processordisposed within the package command node housing of package command node78160, a package command node memory coupled to the package command nodeprocessor and within the package command node housing (maintaining atleast package-level environmental detection program code—program codegoverning operations on package command node 78160 as shown in FIG. 79Awhen detecting and responding to environmental anomalies (e.g., packagecommand node environmental detection program code that is part ofcommand node control and management code 26425 on the memory of packagecommand node 78160). Package command node 78160 shown in FIG. 79A aspart of system 79000 also has a package command node wirelesstransceiver communication interface disposed within the package commandnode housing and operatively responsive to the package command nodeprocessor, the package command node wireless transceiver communicationinterface is configured to communicate with at least each ofsensor-based ID nodes 1-4 within shipping container 24300 a.

The exemplary shipping container command node (command node 1) ismounted to shipping container 24300 a and is operative to communicatewith the package command node 78160 and with an external transceiver(such as external transceiver 24150 or the transceiver-equipped firesuppression system 25010 as shown in FIG. 79A). Exemplary shippingcontainer command node, as an implementation of exemplary command node26000, includes at least a shipping container command node processor, ashipping container command node memory, and a shipping container commandnode wireless transceiver communication interface. In more detail, theshipping container command node memory on command node 1 is coupled tothe shipping container command node processor and maintains at leastshipping container-level environmental detection program code (e.g.,program code that is part of command node control and management code26425 on the memory of shipping container command node 1 shown in FIG.79A). The shipping container command node wireless transceivercommunication interface is operatively responsive to the shippingcontainer command node processor and is configured to communicate withpackage command node 78160 as well as with external transceivers outsideshipping container 24300 (e.g., external transceiver 24150 or thetransceiver-equipped fire suppression system 25010 as shown in FIG.79A).

During system operation of this embodiment, the command node processorof package command node 78160 is programmatically configured, whenexecuting the package-level environmental detection program code, to beoperative to detect the sensor data broadcasted from sensor-based IDnodes 1-4 using the package command node wireless transceivercommunication interface; responsively identify the environmental anomalyfor shipping container 24300 a when the detected sensor data fromsensor-based ID nodes 1-4 indicates an environmental condition thatexceeds an environmental threshold; generate an alert notificationrelated to the environmental anomaly for shipping container 24300 a inresponse to identifying the environmental anomaly for shipping container24300 a; and cause the package command node wireless transceivercommunication interface to transmit the alert notification to theshipping container command node (e.g., command node 1 mounted toshipping container 24300 a).

Furthermore, during system operation of this embodiment, the shippingcontainer command node processor of shipping container command node 1 isprogrammatically configured, when executing the shipping container-levelenvironmental detection program code, to be operative to receive (usingthe shipping container command node wireless transceiver communicationinterface) the alert notification from package command node 78160, andresponsively cause the shipping container command node wirelesstransceiver communication interface to instruct the external transceiver(e.g., external transceiver 24150) to initiate a mediation response forshipping container 24300 a related to the environmental anomaly.

The system's package command node may identify the environmental anomalybased upon sensor data and/or unresponsive ID nodes. For example, thepackage command node processor of package command node 78160 mayresponsively identify the environmental anomaly for shipping container24300 a by being further programmatically configured to responsivelyidentify the environmental anomaly for shipping container 24300 a whenat least one of (a) the detected sensor data from sensor-based ID nodes1-4 indicates an environmental condition that exceeds the environmentalthreshold, and (b) when the detected sensor data from the sensor-basedID nodes 1-4 (i.e., detected sensor data from any of sensor-based IDnodes 1-4) does not include sensor data from at least a threshold numberof sensor-based ID nodes 1-4 as some of the ID node may no longer befunctioning as a result of the environmental anomaly. In more detail,when package command node 78160 maintains context data identifying whichof sensor-based ID nodes 1-4 are anticipated to be broadcasting, thepackage command node processor of package command node 78160 mayidentify the environmental anomaly for shipping container 24300 a bybeing further programmatically configured to responsively identify theenvironmental anomaly for shipping container 24300 a when at least oneof (a) the detected sensor data from sensor-based ID nodes 1-4 indicatesan environmental condition that exceeds the environmental threshold, and(b) when the detected sensor data from those of sensor-based ID nodes1-4 anticipated to be broadcasting according to the context data doesnot include sensor data from at least a threshold number of thesensor-based ID nodes anticipated to be broadcasting.

The context data used by package command node 78160 may be provided bydifferent entities in system 79000. For example, the package commandnode processor of package command node 78160 may be furtherprogrammatically configured to be operative to receive the context datafrom external transceiver 24150 (which may have received the contextdata from remote server 24100). In another example, the shippingcontainer command node memory of command node 1 may maintains thecontext data, provide the context data to package command node 78160 butmay have received such context data from external transceiver 24150(which may have received the context data from remote server 24100).

The system's shipping container command node (i.e., command node 1mounted to shipping container 24300 a) instruct the external transceiverto initiate a mediation response for shipping container 24300 a relatedto the environmental anomaly in several ways. For example, the mediationresponse initiated by shipping container command node 1 may beimplemented as an instruction to external transceiver 24150 to activateonboard triggered fire suppression system 25010 on transit vehicle 24200given external transceiver 24150 is in communication with firesuppression system 25010 as shown in FIG. 79A. In another example, themediation response initiated by shipping container command node 1 may beimplemented as an instruction to external transceiver 24150 to generatea prompted request to change course of transit vehicle 24200 from anexisting travel path of transit vehicle 24200 (e.g., via a visual oraudio prompt generated by external transceiver 24150), or as aninstruction external transceiver 24150 to generate a prompted request toinvestigate the shipping container (e.g., via a visual or audio prompt).In a further embodiment, such a prompted request may take the form of awireless message generated by external transceiver 24150 and transmittedto a user access device (e.g., a handheld communication device, such asa handheld radio transceiver, laptop, ruggedized mobile tablet) used bycrew on transit vehicle 24200).

The system's package command node 78160 may also identify theenvironmental anomaly using only verified/validated ID nodes confirmedto be trusted sensors and/or using only verified or validated sensordata as explained above relative to the embodiment shown in FIG. 78(e.g., the functionality described relative to how exemplary packagecommand node 78160 may use security credentials to validate and confirmwhich of ID nodes 1-4 are trusted sensors and/or use validation recordsto validate what sensor data is trusted sensor data).

Further embodiments of the system shown in FIG. 79A (system 79000 whichhas at least shipping container command node 1, package command node78160, and sensor-based ID nodes 1-4) may involve additional systemoperations of such components when either the shipping command node orthe package command node becomes unresponsive. Referring now to FIG.79B, an example is shown where package command node 78160 has becomeunresponsive and is not functioning as indicated by its inability tocommunicate with shipping container command node 1. This may be due todamage from an environmental anomaly localized to package command node78160 for the time being (but with the likelihood that such anenvironmental anomaly may spread further). As such, an embodiment mayhave the shipping container command node processor of command node 1essentially taking over the primary monitoring operations of the sensordata generated by sensor-based ID nodes 1-4. In more detail, theshipping container command node processor of command node 1 may befurther programmatically configured to be operative, upon detectingpackage command node is unresponsive to a status inquiry message fromshipping container command node a to package command node 78160, todetect the sensor data broadcasted from sensor-based ID nodes 1-4 usingthe shipping container command node wireless transceiver communicationinterface; responsively identify the environmental anomaly for shippingcontainer 24300 a when the detected sensor data from sensor-based IDnodes 1-4 indicates an environmental condition that exceeds anenvironmental threshold; generate the alert notification related to theenvironmental anomaly for shipping container 24300 a in response toidentifying the environmental anomaly for the shipping container; andcause the shipping container command node wireless transceivercommunication interface to transmit the alert notification to anexternal transceiver (e.g., external transceiver 24150 or thetransceiver interface of fire suppression system 25010) to initiate themediation response related to the environmental anomaly.

In an alternative embodiment related to this additional functionality,the shipping container command node 1 may simply generate and transmitthe alert notification to an external transceiver (e.g., externaltransceiver 24150 or the transceiver interface of fire suppressionsystem 25010) to initiate the mediation response related to theenvironmental anomaly immediately upon detecting package command node78160 is unresponsive to a status inquiry message from the shippingcontainer command node. In this way, while one embodiment of the systemhas the shipping container command node taking over monitoringresponsibility when the package command node becomes unresponsive, theother embodiment of the system may deem the unresponsiveness of thepackage command node to be of such importance so as to justify anautomatic and immediate alert notification transmission to initiate anappropriate mediation response. This, in some embodiments, may have theshipping container command node determining to, immediately and withoutfurther monitoring, transmitting the alert notification to initiate theappropriate mediation response depending upon context data (e.g.,shipping information on what type of material is being transportedwithin the package associated with the now unresponsive package commandnode). In other words, if the material in the shipment packageassociated with the package command node is of a predetermined categoryof material (e.g., lithium-ion battery material, combustible material,an extremely flammable material, a certain type of chemical, aradioactive material, and the like) as indicated by context data on theshipping container command node, this fact along with theunresponsiveness of the package command node may have the shippingcontainer command node foregoing further monitoring activity andimmediately transmitting the alert notification to initiate anappropriate mediation response.

Referring now to FIG. 79C, a different example is shown where packagecommand node 78160 is still functional, but shipping container commandnode 1 has become unresponsive and is not functioning as indicated byits inability to communicate with package command node 78160. This maybe due to damage from an environmental anomaly localized to shippingcontainer command node 1 for the time being (but with the likelihoodthat such an environmental anomaly may spread further). As such, anembodiment may have the package command node processor of packagecommand node 78160 essentially taking over alert notification operationsin response to any environmental anomaly detected based on the sensordata generated by sensor-based ID nodes 1-4. In more detail, the packagecommand node processor may be further programmatically configured to beoperative, upon detecting that shipping container command node 1 isunresponsive to a status inquiry message from package command node 78160to shipping container command node 1, to cause the package command nodewireless transceiver communication interface to transmit the alertnotification to an external transceiver (e.g., external transceiver24150 or the transceiver interface of fire suppression system 25010) toinitiate the mediation response related to the environmental anomaly.

It should be emphasized that the sequence of operations to perform anyof the methods and variations of the methods described in theembodiments herein are merely exemplary, and that a variety of sequencesof operations may be followed while still being true and in accordancewith the principles of the present invention.

At least some portions of exemplary embodiments outlined above may beused in association with portions of other exemplary embodiments tobetter monitor for environmental anomalies, enhance detection of variousdifferent types of environmental anomalies, and advantageously initiateselective mediation responses using adaptive, integrated, andcooperative elements of a wireless node network or use such nodes andnetwork elements as part of a hierarchical node network. Moreover, atleast some of the exemplary embodiments disclosed herein may be usedindependently from one another and/or in combination with one anotherand may have applications to devices and methods not disclosed herein.

For example, many of the embodiments above describe using particularwireless communication interfaces when communicating to ID nodes anddifferent wireless communication interfaces when communicating withother node elements of the network (e.g., command nodes, externaltransceivers, onboard fire suppression systems, mobile handheld useraccess devices, and the like). Depending on the type of wirelesstransceiver implemented on a particular node, such a node may be able toperform the same functionality with a single wireless transceiver or anode having two different wireless communication interfaces withoutveering from principles of the described invention herein. Thus, forexample, transmitting a layered alert notification from a command node(e.g., command node 26000, command node 26140, and the like) may beaccomplished with either a first or second communication interface orsimply by a single wireless transceiver-based communication interface(e.g., such as one using LPWAN connectivity) capable of communicationwith ID nodes as well as the other node devices described herein.

Those skilled in the art will readily appreciate that operations of suchan exemplary wireless node network, as set forth herein, are not limitedto detecting a fire within a shipping container on an aircraft, but maybe used to manage logistics related to the packages being transportedwithin the shipping container as well as the transit vehicle itself.

Those skilled in the art will appreciate that embodiments may provideone or more advantages, and not all embodiments necessarily provide allor more than one particular advantage as set forth here. Additionally,it will be apparent to those skilled in the art that variousmodifications and variations can be made to the structures andmethodologies described herein. Thus, it should be understood that theinvention is not limited to the subject matter discussed in thedescription. Rather, the present invention is intended to covermodifications and variations.

1-126. (canceled)
 127. An improved monitoring system for detecting anenvironmental anomaly in a shipping container that maintains a pluralityof packages and for reporting a layered alert notification related tothe environmental anomaly to an external transceiver associated with atransit vehicle transporting the shipping container, the systemcomprising: a plurality of ID nodes disposed within the shippingcontainer, each of the ID nodes being associated with a respective oneof the packages maintained within the shipping container, wherein eachof the ID nodes comprising an ID node processing unit, an ID node memorycoupled to the ID node processing unit, the memory maintaining at leastan ID node monitoring program code, at least one environmental sensorconfigured to generate sensor data related to an environmental conditionof the respective package associated with each of the ID nodes, awireless radio transceiver coupled to the ID node processing unit, thewireless radio transceiver being configured to access the sensor datagenerated by the at least one environmental sensor and broadcast thesensor data in response to a report command from the ID node processingunit when the ID node processing unit executes the ID node monitoringprogram code; and a command node comprising a mobile master nodedisposed with the shipping container, the command node furthercomprising a command node processing unit, a command node memory coupledto the command node processing unit, the command node memory maintainingat least command node container management program code and context datarelated to each of the ID nodes, the context data including at least aplurality of environmental threshold conditions respectivelycorresponding to each of the packages, a first communication interfacecoupled to the command node processing unit, the first communicationinterface being configured to communicate with each of the ID nodesusing a first wireless communication format compatible with the wirelessradio transceiver on each of the ID nodes, a second communicationinterface coupled to the command node processing unit, the secondcommunication interface being configured to communicate with theexternal transceiver associated with a transit vehicle using a secondwireless communications format; wherein the command node processing unitis programmatically configured, when executing the command nodecontainer management program code, to be operative to detect the sensordata broadcasted from the ID nodes using the first communicationinterface, compare the detected sensor data from each of the ID nodesand the context data related to each of the ID nodes, detect theenvironmental anomaly for the shipping container when the comparison ofthe detected sensor data and the context data indicates an environmentalcondition for at least one of the packages exceeds its respectiveenvironmental threshold condition, generate a layered alert notificationrelated to the environmental anomaly for the shipping container inresponse to detecting the environmental anomaly, wherein the layeredalert notification identifies a targeted mediation recipient, identifiesa targeted mediation action, and establishes a mediation responsepriority based upon the comparison of the received sensor data and thecontext data, and cause the second communication interface to transmitthe layered alert notification to the transceiver unit to initiate amediation response related to the targeted mediation action.
 128. Thesystem of claim 127, wherein the command node processing unit is furtherprogrammatically configured to detect the environmental anomaly for theshipping container when the comparison of the detected sensor data andthe context data indicates a relative change in the environmentalcondition for the at least one of the packages exceeds its respectiveenvironmental threshold condition.
 129. The system of claim 127, whereinthe command node processing unit is further programmatically configuredto compare the detected sensor data and the context data further bycomparing a relative change in the detected sensor data from at leastone of the ID nodes and the context data locally maintained in thecommand node memory for the at least one of the ID nodes, wherein the atleast one of the ID nodes being associated with the at least one of thepackages, wherein the environmental threshold condition for the at leastone of the packages comprising a threshold relative environmental changecondition that when exceeded is indicative of the environmental anomalyfor the shipping container; and wherein the command node processing unitis further programmatically configured to detect the environmentalanomaly for the shipping container when the comparison of the detectedsensor data and the context data indicates the environmental conditionfor the at least one of the packages associated with the at least one ofthe ID nodes exceeds the threshold relative environmental changecondition.
 130. The system of claim 127, wherein each of the ID nodes isfurther operative to incrementally generate the sensor data over a timeperiod using the environmental sensor on each of the respective IDnodes; wherein the command node processing unit is furtherprogrammatically configured to monitor the generated sensor data fromeach of the ID nodes over the time period to identify relative changesin the generated sensor data over the time period, compare theidentified relative changes in the generated sensor data and the contextdata locally maintained on the command node memory related to those ofthe ID nodes that are related to the relative changes in the generatedsensor data, the context data including at least a plurality of relativeenvironmental threshold conditions respectively corresponding to thepackages, detect the environmental anomaly for the shipping containerwhen the comparison of identified relative changes in the generatedsensor data and the context data related to those of the ID nodes thatcorrespond to the identified relative changes in the generated sensordata indicates a changed environmental condition for at least one of thepackages that exceeds its respective relative environmental thresholdcondition, and wherein the mediation response priority is based upon thecomparison of the identified relative changes in the generated sensordata and the context data related to those of the ID nodes thatcorrespond to the relative changes in the generated sensor data. 131.The system of claim 127, wherein the environmental sensor for a first ofthe ID nodes comprises a temperature sensor and the environmental sensorfor a second of the ID nodes comprises a barometric pressure sensor.132. The system of claim 131, wherein the command node processing unitis further programmatically configured to detect the environmentalanomaly when: (a) the sensor data detected from the first of the IDnodes comprises a temperature value; (b) the sensor data detected fromthe second of the ID nodes comprises a barometric pressure value; (c)the temperature value indicates the environmental condition of a firstpackage associated with the first of the ID nodes exceeds theenvironmental threshold condition for the first package according to thecontext data for the first package; and (d) the barometric pressurevalue indicates the environmental condition of a second packageassociated with the second of the ID nodes exceeds the environmentalthreshold condition for the second package according to the context datafor the second package.
 133. The system of claim 127, wherein theenvironmental sensor for a first of the ID nodes comprises a temperaturesensor and the environmental sensor for a second of the ID nodescomprises one from a group consisting of a barometric pressure sensor, aradiation sensor, and a chemical sensor.
 134. The system of claim 127,wherein the environmental sensor for a first of the ID nodes comprises aplurality of sensor elements, the sensor elements comprising at least atemperature sensor element and a barometric pressure sensor element.135. The system of claim 133, wherein the command node processing unitis further programmatically configured to detect the environmentalanomaly when: (a) the sensor data detected from the first of the IDnodes comprises a temperature value; (b) the sensor data detected fromthe second of the ID nodes comprises an environmental condition value ofone of a sensed barometric pressure level by the barometric sensor, adetected radiation level by the radiation sensor, or a detected chemicalby the chemical sensor; (c) the temperature value indicates theenvironmental condition of a first package associated with the first ofthe ID nodes exceeds the environmental threshold condition for the firstpackage according to the context data for the first package; and (d) theenvironmental condition value indicates the environmental condition of asecond package associated with the second of the ID nodes exceeds theenvironmental threshold condition for the second package according tothe context data for the second package.
 136. The system of claim 135,wherein the detected chemical is indicative of an explosive.
 137. Thesystem of claim 135, wherein the detected chemical is indicative of afire.
 138. The system of claim 137, wherein the detected chemicalcomprises one of either CO or CO₂.
 139. The system of claim 132, whereinthe detected environmental anomaly for the shipping container comprisesa fire within the shipping container when the temperature value exceedsa temperature threshold maintained by the command node in the commandnode memory as part of the context data for the first package and whenthe barometric pressure value exceeds a pressure threshold maintained bythe command node in the command node memory as part of the context datafor the second package.
 140. The system of claim 132, wherein thedetected environmental anomaly for the shipping container comprises anexplosion within the shipping container when the temperature valueexceeds a temperature threshold maintained by the command node in thecommand node memory as part of the context data for the first packageand when the barometric pressure value is below a pressure thresholdmaintained by the command node in the command node memory as part of thecontext data for the second package.
 141. The system of claim 132,wherein the detected environmental anomaly for the shipping containercomprises an explosion within the shipping container when thetemperature value exceeds a temperature threshold maintained by thecommand node in the command node memory as part of the context data forthe first package and when the barometric pressure value drops fasterthan a pressure drop threshold maintained by the command node in thecommand node memory as part of the context data for the second package.142. The system of claim 135, wherein the detected environmental anomalyfor the shipping container comprises a detected chemical related firewithin the shipping container when the temperature value exceeds atemperature threshold maintained by the command node in the command nodememory is part of the context data for the first package and when thedetected chemical matches a predetermined chemical profile maintained bythe command node in the command node memory as part of the context datafor the second package.
 143. The system of claim 135, wherein thedetected environmental anomaly for the shipping container comprises aradiation leak within the shipping container when the temperature valueexceeds a temperature threshold maintained by the command node as partof the context data for the first package and when the detectedradiation matches a predetermined radiation profile maintained by thecommand node as part of the context data for the second package. 144.The system of claim 127, wherein the step of broadcasting the generatedsensor data by the ID nodes comprises transmitting, by each of the IDnodes, the generated sensor data according to a broadcast profilemaintained by each of the ID nodes, the broadcast profile defining afirst messaging rate used to regulate how often the generated sensordata is transmitted to the command node, the first messaging rate beinghigher than a default messaging rate; and further comprising the step ofinstructing, by the command node, each of the ID nodes to broadcastfuture generated sensor data at a second messaging rate that exceeds thefirst messaging rate after transmitting the layered alert notificationto the transceiver unit.
 145. The system of claim 144, wherein thecommand node is further programmatically configured to instructing, bythe command node, each of the ID nodes to change from the defaultmessaging rate to the first messaging rate.
 146. The system of claim144, wherein the first messaging rate for the ID nodes comprises aninitial value correlated to an environmental risk associated with atleast one of the packages within the shipping container.
 147. The systemof claim 146, wherein the second messaging rate for the ID nodescomprises a predetermined messaging rate based upon a type of materialexisting within at least one of the packages within the shippingcontainer.
 148. The system of claim 127, wherein the command node isfurther programmatically configured to automatically select the targetedmediation recipient based upon an excess condition on how much thedetected sensor data and the context data indicates the environmentalcondition for the at least one of the packages exceeds the environmentalthreshold condition for the at least one of the packages.
 149. Thesystem of claim 148, wherein the targeted mediation recipient identifiedby the command node in the layered alert notification comprises atriggered fire suppression system on the transit vehicle that isoperative to automatically respond to the detected environmental anomalybased upon receipt of the layered alert notification.
 150. The system ofclaim 148, wherein the targeted mediation recipient identified by thecommand node in the layered alert notification comprises an operator ofthe transit vehicle that can alter movement of the transit vehicle. 151.The system of claim 148, wherein the targeted mediation recipientidentified by the command node in the layered alert notificationcomprises a logistics crew member of the transit vehicle that caninspect the shipping container.
 152. The system of claim 127, whereinthe targeted mediation action is automatically selected by the commandnode based upon an excess condition on how much the detected sensor dataand the context data indicates the environmental condition for the atleast one of the packages exceeds the environmental threshold conditionfor the at least one of the packages.
 153. The system of claim 127,wherein the targeted mediation action identified by the command node inthe layered alert notification depends upon what is loaded within theshipping container as indicated by shipping information maintained onthe command node.
 154. The system of claim 127, wherein the targetedmediation action identified by the command node in the layered alertnotification depends upon an excess condition on how many of thepackages have their detected sensor data and their context dataindicating that their environmental condition exceed the environmentalthreshold condition for the packages.
 155. The system of claim 127,wherein the command node processing unit is further programmaticallyconfigured to receive vehicle status data from the external transceiverof the transit vehicle using the second communication interface andmaintain the vehicle status data in the command node memory; and whereinthe targeted mediation action identified in the layered alertnotification depends upon a state of the transit vehicle as indicated bythe vehicle status data.
 156. The system of claim 155, wherein the stateof the transit vehicle comprises one from the group of a takeoffvehicular status, a cruising vehicular status, a landing vehicularstatus, and an on-the-ground vehicular status.
 157. The system of claim127, wherein the command node memory further maintains container statusdata corresponding to the shipping container; and wherein the targetedmediation action in the layered alert notification depends upon a stateof the shipping container as indicated in the container status data.158. The system of claim 127, wherein the command node further compriseslocation circuitry coupled to the command node processing unit, thelocation circuitry being operative to detect geolocation data related toa current location of the shipping container within the transit vehicle;and wherein the targeted mediation action identified in the layeredalert notification depends upon the current location of the shippingcontainer as indicated in the geolocation data.
 159. The system of claim127, wherein the command node memory further maintains loading plan dataindicating the relative location of shipping container within thetransit vehicle; and wherein the targeted mediation action identified bythe command node in the layered alert notification depends upon therelative location of the shipping container within the transit vehicleas indicated in the loading plan data.
 160. The system of claim 127,wherein the command node memory further maintains facility status dataassociated with a storage facility for the shipping container; andwherein the targeted mediation action identified by the command node inthe layered alert notification depends upon a state of the storagefacility as indicated in the facility status data.
 161. The system ofclaim 152, wherein the targeted mediation response in the layered alertnotification comprises an automatic response to be performed by atriggered fire suppression system on the transit vehicle.
 162. Thesystem of claim 152, wherein the targeted mediation response in thelayered alert notification comprises a request to change course of thetransit vehicle from an existing travel path of the transit vehicle.163. The system of claim 152, wherein the targeted mediation response inthe layered alert notification comprises a request to investigate theshipping container.
 164. The system of claim 127, wherein the mediationresponse priority is automatically selected by the command nodeprocessing unit when generating the layered alert notification basedupon an excess condition on how much the detected sensor data and thecontext data indicates the environmental condition for the at least oneof the packages exceeds the environmental threshold condition for the atleast one of the packages.
 165. The system of claim 164, wherein themediation response priority established by the command node as part ofthe layered alert notification comprises a high priority levelindicating further travel by the transit vehicle is to be at leastminimized when responding to the detected environmental anomaly. 166.The system of claim 164, wherein the mediation response priorityestablished by the command node as part of the layered alertnotification comprises an intermediate priority level indicating furthertravel by the transit vehicle is permissible when responding to thedetected environmental anomaly.
 167. The system of claim 127, whereinthe transit vehicle comprises an aircraft.
 168. The system of claim 127,wherein the transit vehicle comprises one from the group consisting of arailway conveyance, a maritime vessel, and a roadway conveyance. 169.The system of claim 127, wherein each of the ID nodes travel withrespective ones of the packages.
 170. The system of claim 127, whereinat least one of the ID nodes is affixed to the outside of one of thepackages.
 171. The system of claim 127, wherein at least one of the IDnodes is integrated as part of one of the packages.
 172. The system ofclaim 127, wherein the command node processing unit is furtherprogrammatically configured to select each of the ID nodes from a largergroup of network elements being loaded into the shipping container, theID nodes that are selected providing the gathered sensor data for use indetecting the environmental anomaly for the shipping container.
 173. Thesystem of claim 172, wherein the command node processing unit is furtherprogrammatically configured to identify each of the ID nodes selectedbased upon package content information maintained within the commandnode memory.
 174. The system of claim 172, wherein the command nodeprocessing unit is further programmatically configured to identify eachof the ID nodes selected based upon loading plan data maintained withinthe command node memory.
 175. The system of claim 127, wherein thecommand node processing unit is further programmatically configured toreceive an update for the environmental threshold conditions for atleast one of the packages using the second communication interface. 176.The system of claim 175, wherein the update for the environmentalthreshold conditions is received by the second communication interfacefrom the external transceiver.
 177. The system of claim 176, wherein theupdate for the environmental threshold conditions is defined by anoperator of the transit vehicle using the external transceiver.
 178. Thesystem of claim 176, wherein the update for the environmental thresholdconditions is defined by a logistics crew member of the transit vehicleusing the external transceiver.
 179. The system of claim 176, whereinthe update for the environmental threshold conditions is provided to theexternal transceiver from a remote control center in communication withthe external transceiver.
 180. The system of claim 127, wherein thecommand node processing unit is further programmatically configured soas to detect the sensor data using the first communication interface bybeing operative to: (a) receive the sensor data broadcasted from a firstof the ID nodes using the first communication interface; (b) confirm thevalidity of the received sensor data; (c) repeat (a) and (b) for theremainder of the sensor data received from any of the remaining ones ofthe ID nodes using the first communication interface; and (d)selectively compile the detected sensor data using only the receivedsensor data confirmed valid.
 181. The system of claim 180, wherein thecommand node processor is programmatically configured to confirm thevalidity of the received sensor data by being further operative to:cause the first communication interface to send an authenticationrequest to the first of the ID nodes; and receive a validation responsefrom the first of the ID nodes via the first communication interface,wherein the validation response authenticates the sensor databroadcasted from the first of the ID nodes.
 182. The system of claim180, wherein the command node processor is programmatically configuredto confirm the validity of the received sensor data by being furtheroperative to: access a validation sequence for the first of the IDnodes, the validation sequence being maintained by the command nodememory and characterizing expected broadcasts from the first of the IDnodes; and determine if the received sensor data from the first of theID nodes matches a predetermined one of the expected broadcasts from thefirst of the ID nodes according to the validation sequence stored withinthe command node memory.
 183. The system of claim 182, wherein thepredetermined one of the expected broadcasts comprises a rotating valuepreviously received by the command node for the first of the ID nodes.184. The system of claim 127, wherein the mobile master node ispermanently mounted to the shipping container.
 185. The system of claim127, wherein the mobile master node is integrated as part of theshipping container.
 186. The system of claim 127, wherein the mobilemaster node is implemented separately from the shipping container andtemporarily mounted to the shipping container.
 187. The system of claim186, wherein the mobile master node is temporarily mounted to theshipping container within a shipment pouch disposed on the shippingcontainer.
 188. The system of claim 127, wherein the mobile master nodecomprises location circuitry that allows the mobile master node toself-locate.
 189. The system of claim 127, wherein the at least oneenvironmental sensor on each of the ID nodes comprises at least one froma group consisting of a movement sensor, an acceleration sensor, analtitude sensor, an attitude sensor, and an orientation sensor.
 190. Thesystem of claim 127, wherein the at least one environmental sensor oneach of the ID nodes comprises at least one from a group consisting of alight sensor and a humidity sensor.
 191. The system of claim 127,wherein the at least one environmental sensor on each of the ID nodescomprises at least one from a group consisting of a chemical sensor, aradiation sensor, and a magnetic field sensor.
 192. The system of claim127, wherein the at least one environmental sensor on each of the IDnodes comprises at least two from a group consisting of a temperaturesensor, a barometric pressure sensor, a movement sensor, an accelerationsensor, an altitude sensor, an attitude sensor, an orientation sensor, alight sensor, a humidity sensor, a chemical sensor, a radiation sensor,and a magnetic field sensor.
 193. An improved method for monitoring ashipping container and responding to an environmental anomaly using awireless node network having at least a plurality of ID nodes disposedwithin the shipping container and a command node implemented as a mobilemaster node disposed with the shipping container, each of the ID nodeshaving at least one environmental sensor and being associated with arespective one of a plurality of packages maintained within the shippingcontainer, and wherein the command node being operative to communicatewith each of the ID nodes and an external transceiver associated with atransit vehicle, the method comprising: generating, by the environmentalsensor on each of the ID nodes, sensor data related to an environmentalcondition of the respective package associated with each of the ID nodesas the packages reside within the shipping container; broadcasting, byeach of the ID nodes, the generated sensor data; detecting, by themobile master node operating as the command node, the sensor databroadcasted from the ID nodes; comparing, by the mobile master nodeoperating as the command node, the detected sensor data from each of theID nodes and locally maintained context data related to each of the IDnodes, the context data including at least a plurality of environmentalthreshold conditions respectively corresponding to the packages;detecting, by the mobile master node operating as the command node, theenvironmental anomaly for the shipping container when the comparison ofthe detected sensor data and the context data indicates an environmentalcondition for at least one of the packages exceeds its respectiveenvironmental threshold condition; generating, by the mobile master nodeoperating as the command node, a layered alert notification related tothe environmental anomaly for the shipping container in response todetecting the environmental anomaly, wherein the layered alertnotification identifies a targeted mediation recipient, identifies atargeted mediation action, and establishes a mediation response prioritybased upon the comparison of the received sensor data and the contextdata; and transmitting, by the mobile master node operating as thecommand node, the layered alert notification to the transceiver unit toinitiate a mediation response related to the targeted mediation action.194. The method of claim 193, wherein the step of detecting theenvironmental anomaly for the shipping container occurs when thecomparison of the detected sensor data and the context data indicates arelative change in the environmental condition for the at least one ofthe packages exceeds its respective environmental threshold condition.195. The method of claim 193, wherein the step of comparing the detectedsensor data and the context data further comprises comparing, by themobile master node operating as the command node, a relative change inthe detected sensor data from at least one of the ID nodes and thelocally maintained context data for the at least one of the ID nodes,wherein the at least one of the ID nodes being associated with the atleast one of the packages, wherein the environmental threshold conditionfor the at least one of the packages comprising a threshold relativeenvironmental change condition that when exceeded is indicative of theenvironmental anomaly for the shipping container; and wherein the stepof detecting the environmental anomaly for the shipping container occurswhen the comparison of the detected sensor data and the context dataindicates the environmental condition for the at least one of thepackages associated with the at least one of the ID nodes exceeds thethreshold relative environmental change condition.
 196. The method ofclaim 193, wherein the step of generating the sensor data furthercomprises incrementally generating, by the environmental sensor on eachof the ID nodes, the sensor data over a time period; wherein the step ofdetecting the generated sensor data broadcasted from each of the IDnodes comprises incrementally monitoring, by the mobile master nodeoperating as the command node, the generated sensor data from each ofthe ID nodes over the time period to identify relative changes in thegenerated sensor data over the time period; wherein the comparing stepcomprises comparing, by the mobile master node operating as the commandnode, the identified relative changes in the generated sensor data andlocally maintained context data related to those of the ID nodes thatare related to the relative changes in the generated sensor data, thecontext data including at least a plurality of relative environmentalthreshold conditions respectively corresponding to the packages; whereinthe step of detecting the environmental anomaly for the shippingcontainer occurs when the comparison of identified relative changes inthe generated sensor data and locally maintained context data related tothose of the ID nodes that correspond to each of the identified relativechanges in the generated sensor data indicates a changed environmentalcondition for at least one of the packages exceeds its respectiverelative environmental threshold condition; and wherein the mediationresponse priority is based upon the comparison of the identifiedrelative changes in the generated sensor data and the locally maintainedcontext data related to those of the ID nodes that correspond to therelative changes in the generated sensor data.
 197. The method of claim193, wherein the environmental sensor for a first of the ID nodescomprises a temperature sensor and the environmental sensor for a secondof the ID nodes comprises a barometric pressure sensor.
 198. The methodof claim 197, wherein the step of detecting the environmental anomalyfurther comprises detecting the environmental anomaly when (a) thesensor data detected from the first of the ID nodes comprises atemperature value; (b) the sensor data detected from the second of theID nodes comprises a barometric pressure value; (c) the temperaturevalue indicates the environmental condition of a first packageassociated with the first of the ID nodes exceeds the environmentalthreshold condition for the first package according to the context datafor the first package; and (d) the barometric pressure value indicatesthe environmental condition of a second package associated with thesecond of the ID nodes exceeds the environmental threshold condition forthe second package according to the context data for the second package.199. The method of claim 193, wherein the environmental sensor for afirst of the ID nodes comprises a temperature sensor and theenvironmental sensor for a second of the ID nodes comprises one from agroup consisting of a barometric pressure sensor, a radiation sensor,and a chemical sensor.
 200. The method of claim 193, wherein theenvironmental sensor for a first of the ID nodes comprises a pluralityof sensor elements, the sensor elements comprising at least atemperature sensor element and a barometric pressure sensor element.201. The method of claim 199, wherein the step of detecting theenvironmental anomaly further comprises detecting the environmentalanomaly when (a) the sensor data detected from the first of the ID nodescomprises a temperature value; (b) the sensor data detected from thesecond of the ID nodes comprises an environmental condition value of oneof a sensed barometric pressure level by the barometric sensor, adetected radiation level by the radiation sensor, or a detected chemicalby the chemical sensor; (c) the temperature value indicates theenvironmental condition of a first package associated with the first ofthe ID nodes exceeds the environmental threshold condition for the firstpackage according to the context data for the first package; and (d) theenvironmental condition value indicates the environmental condition of asecond package associated with the second of the ID nodes exceeds theenvironmental threshold condition for the second package according tothe context data for the second package.
 202. The method of claim 201,wherein the detected chemical is indicative of an explosive.
 203. Themethod of claim 201, wherein the detected chemical is indicative of afire.
 204. The method of claim 203, wherein the detected chemicalcomprises one of either CO or CO₂.
 205. The method of claim 198, whereinthe detected environmental anomaly for the shipping container comprisesa fire within the shipping container when the temperature value exceedsa temperature threshold maintained by the command node as part of thecontext data for the first package and when the barometric pressurevalue exceeds a pressure threshold maintained by the command node aspart of the context data for the second package.
 206. The method ofclaim 198, wherein the detected environmental anomaly for the shippingcontainer comprises an explosion within the shipping container when thetemperature value exceeds a temperature threshold maintained by thecommand node as part of the context data for the first package and whenthe barometric pressure value is below a pressure threshold maintainedby the command node as part of the context data for the second package.207. The method of claim 198, wherein the detected environmental anomalyfor the shipping container comprises an explosion within the shippingcontainer when the temperature value exceeds a temperature thresholdmaintained by the command node as part of the context data for the firstpackage and when the barometric pressure value drops faster than apressure drop threshold maintained by the command node as part of thecontext data for the second package.
 208. The method of claim 201,wherein the detected environmental anomaly for the shipping containercomprises a detected chemical related fire within the shipping containerwhen the temperature value exceeds a temperature threshold maintained bythe command node as part of the context data for the first package andwhen the detected chemical matches a predetermined chemical profilemaintained by the command node as part of the context data for thesecond package.
 209. The method of claim 201, wherein the detectedenvironmental anomaly for the shipping container comprises a radiationleak within the shipping container when the temperature value exceeds atemperature threshold maintained by the command node as part of thecontext data for the first package and when the detected radiationmatches a predetermined radiation profile maintained by the command nodeas part of the context data for the second package.
 210. The method ofclaim 193, wherein the step of broadcasting the generated sensor data bythe ID nodes comprises transmitting, by each of the ID nodes, thegenerated sensor data according to a broadcast profile maintained byeach of the ID nodes, the broadcast profile defining a first messagingrate used to regulate how often the generated sensor data is transmittedto the command node, the first messaging rate being higher than adefault messaging rate; and further comprising the step of instructing,by the mobile master node operating as the command node, each of the IDnodes to broadcast future generated sensor data at a second messagingrate that exceeds the first messaging rate after transmitting thelayered alert notification to the transceiver unit.
 211. The method ofclaim 210 further comprising instructing, by the command node, each ofthe ID nodes to change from the default messaging rate to the firstmessaging rate.
 212. The method of claim 210, wherein the firstmessaging rate for the ID nodes comprises an initial value correlated toan environmental risk associated with at least one of the packageswithin the shipping container.
 213. The method of claim 212, wherein thesecond messaging rate for the ID nodes comprises a predeterminedmessaging rate based upon a type of material existing within at leastone of the packages within the shipping container.
 214. The method ofclaim 193, wherein the targeted mediation recipient is automaticallyselected by the command node based upon an excess condition on how muchthe detected sensor data and the context data indicates theenvironmental condition for the at least one of the packages exceeds theenvironmental threshold condition for the at least one of the packages.215. The method of claim 214, wherein the targeted mediation recipientidentified by the command node in the layered alert notificationcomprises a triggered fire suppression system on the transit vehiclethat is operative to automatically respond to the detected environmentalanomaly based upon receipt of the layered alert notification.
 216. Themethod of claim 214, wherein the targeted mediation recipient identifiedby the command node in the layered alert notification comprises anoperator of the transit vehicle that can alter movement of the transitvehicle.
 217. The method of claim 214, wherein the targeted mediationrecipient identified by the command node in the layered alertnotification comprises a logistics crew member of the transit vehiclethat can inspect the shipping container.
 218. The method of claim 193,wherein the targeted mediation action is automatically selected by thecommand node based upon an excess condition on how much the detectedsensor data and the context data indicates the environmental conditionfor the at least one of the packages exceeds the environmental thresholdcondition for the at least one of the packages.
 219. The method of claim193, wherein the targeted mediation action identified by the commandnode in the layered alert notification depends upon what is loadedwithin the shipping container as indicated by shipping informationmaintained on the command node.
 220. The method of claim 193, whereinthe targeted mediation action identified by the command node in thelayered alert notification depends upon an excess condition on how manyof the packages have their detected sensor data and their context dataindicating that their environmental condition exceed the environmentalthreshold condition for the packages.
 221. The method of claim 193further comprising the step of receiving, by the mobile master nodeoperating as the command node, vehicle status data from the externaltransceiver associated with the transit vehicle; and wherein thetargeted mediation action identified by the command node in the layeredalert notification depends upon a state of the transit vehicle asindicated by the vehicle status data.
 222. The method of claim 221,wherein the state of the transit vehicle comprises one from the group ofa takeoff vehicular status, a cruising vehicular status, a landingvehicular status, and an on-the-ground vehicular status.
 223. The methodof claim 193 further comprising the step of accessing, by the mobilemaster node operating as the command node, container status datamaintained by the command node and associated with the shippingcontainer; and wherein the targeted mediation action identified by thecommand node in the layered alert notification depends upon a state ofthe shipping container as indicated in the container status data. 224.The method of claim 193 further comprising the step of detecting, by themobile master node operating as the command node, geolocation datarelated to a current location of the shipping container within thetransit vehicle; and wherein the targeted mediation action identified bythe command node in the layered alert notification depends upon thecurrent location of the shipping container as indicated in thegeolocation data.
 225. The method of claim 193 further comprising thestep of accessing, by the mobile master node operating as the commandnode, loading plan data maintained by the command node, the loading plandata indicating a relative location of the shipping container within thetransit vehicle; and wherein the targeted mediation action identified bythe command node in the layered alert notification depends upon therelative location of the shipping container within the transit vehicleas indicated in the loading plan data.
 226. The method of claim 193further comprising the step of accessing, by the mobile master nodeoperating as the command node, facility status data maintained by thecommand node and associated with a storage facility for the shippingcontainer; and wherein the targeted mediation action identified by thecommand node in the layered alert notification depends upon a state ofthe storage facility as indicated in the facility status data.
 227. Themethod of claim 218, wherein the targeted mediation response identifiedby the command node in the layered alert notification comprises anautomatic response by a triggered fire suppression system on the transitvehicle.
 228. The method of claim 218, wherein the targeted mediationresponse identified by the command node in the layered alertnotification comprises a request to change course of the transit vehiclefrom an existing travel path of the transit vehicle.
 229. The method ofclaim 218, wherein the targeted mediation response identified by thecommand node in the layered alert notification comprises a request toinvestigate the shipping container.
 230. The method of claim 193,wherein the mediation response priority is automatically selected by thecommand node based upon an excess condition on how much the detectedsensor data and the context data indicates the environmental conditionfor the at least one of the packages exceeds the environmental thresholdcondition for the at least one of the packages.
 231. The method of claim230, wherein the mediation response priority established by the commandnode as part of the layered alert notification comprises a high prioritylevel indicating further travel by the transit vehicle is to be at leastminimized when responding to the detected environmental anomaly. 232.The method of claim 230, wherein the mediation response priorityestablished by the command node as part of the layered alertnotification comprises an intermediate priority level indicating furthertravel by the transit vehicle is permissible when responding to thedetected environmental anomaly.
 233. The method of claim 193, whereinthe transit vehicle comprises an aircraft.
 234. The method of claim 193,wherein the transit vehicle comprises one from the group consisting of arailway conveyance, a maritime vessel, and a roadway conveyance. 235.The method of claim 193, wherein the command node is integrated as partof the shipping container.
 236. The method of claim 193, wherein each ofthe ID nodes travel with respective ones of the packages.
 237. Themethod of claim 193, wherein at least one of the ID nodes is affixed tothe outside of one of the packages.
 238. The method of claim 193,wherein at least one of the ID nodes is integrated as part of one of thepackages.
 239. The method of claim 193 further comprising the step ofselecting, by the mobile master node operating as the command node, eachof the ID nodes from a larger group of network elements being loadedinto the shipping container, the ID nodes that are selected providingthe gathered sensor data for use in detecting the environmental anomalyfor the shipping container.
 240. The method of claim 239, wherein the IDnodes selected are identified for selection by the command node basedupon contents of the packages associated with the ID nodes beingselectively activated.
 241. The method of claim 239, wherein the IDnodes selected are identified for selection by the command node basedupon a loading scheme for the shipping container, the loading schemebeing maintained in memory of the command node as loading plan data.242. The method of claim 193 further comprising receiving, by the mobilemaster node operating as the command node, an update for theenvironmental threshold conditions for at least one of the packages.243. The method of claim 242, wherein the update for the environmentalthreshold conditions is received from the external transceiver.
 244. Themethod of claim 243, wherein the update for the environmental thresholdconditions is defined by an operator of the transit vehicle using theexternal transceiver.
 245. The method of claim 243, wherein the updatefor the environmental threshold conditions is defined by a logisticscrew member of the transit vehicle using the external transceiver. 246.The method of claim 243, wherein the update for the environmentalthreshold conditions is provided to the external transceiver from aremote control center in communication with the external transceiver.247. The method of claim 193, wherein the step of detecting the sensordata further comprises: (a) receiving, by the mobile master nodeoperating as the command node, the sensor data broadcasted from a firstof the ID nodes; (b) confirming, by the mobile master node operating asthe command node, the validity of the received sensor data; (c)repeating steps (a) and (b), by the mobile master node operating as thecommand node, for the remainder of the sensor data received from any ofthe remaining ones of the ID nodes; and (d) compiling the detectedsensor data using only the received sensor data confirmed valid in step(b).
 248. The method of claim 247, wherein the step of confirming thevalidity of the received sensor data further comprises: sending, by themobile master node operating as the command node, an authenticationrequest to the first of the ID nodes; and receiving, by the mobilemaster node operating as the command node, a validation response fromthe first of the ID nodes that authenticates the sensor data broadcastedfrom the first of the ID nodes.
 249. The method of claim 247, whereinthe step of confirming the validity of the received sensor data furthercomprises accessing, by the mobile master node operating as the commandnode, a validation sequence for the first of the ID nodes, thevalidation sequence being maintained by the command node andcharacterizing expected broadcasts from the first of the ID nodes; anddetermining if the received sensor data from the first of the ID nodesmatches a predetermined one of the expected broadcasts from the first ofthe ID nodes according to the validation sequence stored within thecommand node.
 250. The method of claim 249, wherein the predeterminedone of the expected broadcasts comprises a rotating value previouslyreceived by the command node for the first of the ID nodes.
 251. Themethod of claim 193, wherein the mobile master node operating as thecommand node is temporarily mounted to the shipping container within ashipment pouch disposed on the shipping container.
 252. The method ofclaim 193, wherein the step of generating the sensor data is performed,as the environmental sensor on each of the ID nodes, by at least onefrom a group consisting of a movement sensor, an acceleration sensor, analtitude sensor, an attitude sensor, and an orientation sensor.
 253. Themethod of claim 193, wherein the step of generating the sensor data isperformed, as the environmental sensor on each of the ID nodes, by atleast one from a group consisting of a light sensor and a humiditysensor.
 254. The method of claim 193, wherein the step of generating thesensor data is performed, as the environmental sensor on each of the IDnodes, by at least one from a group consisting of a chemical sensor, aradiation sensor, and a magnetic field sensor.
 255. The method of claim193, wherein the step of generating the sensor data is performed, as theenvironmental sensor on each of the ID nodes, by at least two from agroup consisting of a temperature sensor, a barometric pressure sensor,a movement sensor, an acceleration sensor, an altitude sensor, anattitude sensor, an orientation sensor, a light sensor, a humiditysensor, a chemical sensor, a radiation sensor, and a magnetic fieldsensor.
 256. An improved system for detecting and automaticallyreporting on an environmental anomaly in a shipping container onboard atransit vehicle, the shipping container maintaining a plurality ofpackages, the system comprising: a plurality of ID sensor nodes disposedwithin the shipping container, each of the ID sensor nodes beingassociated with a respective one of the packages maintained within theshipping container, wherein each of the ID sensor nodes comprising an IDsensor node processing unit, an ID sensor node memory coupled to the IDsensor node processing unit, the memory maintaining at least an IDsensor node monitoring program code, at least one environmental sensorconfigured to generate sensor data related to an environmental conditionof the respective package associated with each of the ID sensor nodes, awireless radio transceiver coupled to the ID sensor node processingunit, the wireless radio transceiver being configured to access thesensor data generated by the at least one environmental sensor andbroadcast the sensor data in response to a report command from the IDsensor node processing unit when the ID sensor node processing unitexecutes the ID sensor node monitoring program code; and a command nodeimplemented as a mobile master node disposed with the shippingcontainer, the command node further comprising a command node processingunit, a command node memory coupled to the command node processing unit,the command node memory maintaining at least command node containermanagement program code and context data related to each of the IDsensor nodes, the context data including at least a plurality ofenvironmental threshold conditions respectively corresponding to each ofthe packages, a first communication interface coupled to the commandnode processing unit, the first communication interface being configuredto communicate with each of the ID sensor nodes using a first wirelesscommunication format compatible with the wireless radio transceiver oneach of the ID sensor nodes, a second communication interface coupled tothe command node processing unit, the second communication interfacebeing configured to communicate over a second wireless communicationsformat; and a transit vehicle transceiver in communication with thesecond communication interface of the command node, the transit vehicletransceiver comprising at least a display interface and a firesuppression system interface; wherein the command node processing unitis programmatically configured, when executing the command nodecontainer management program code, to be operative to detect the sensordata broadcasted from the ID sensor nodes using the first communicationinterface, compare the detected sensor data from each of the ID sensornodes and the context data related to each of the ID sensor nodes,detect the environmental anomaly for the shipping container when thecomparison of the detected sensor data and the context data indicates anenvironmental condition for at least one of the packages exceeds itsrespective environmental threshold condition, generate a layered alertnotification related to the environmental anomaly for the shippingcontainer in response to detecting the environmental anomaly, whereinthe layered alert notification identifies a targeted mediationrecipient, identifies a targeted mediation action, and establishes amediation response priority based upon the comparison of the receivedsensor data and the context data, and cause the second communicationinterface to transmit the layered alert notification to the transitvehicle transceiver to initiate a mediation response related to thetargeted mediation action. wherein the transit vehicle transceiver, inresponse to receiving the layered alert notification, is operative toautomatically generate a mediation message as the mediation response,the mediation message reflecting the targeted mediation action and themediation response priority, and provide the mediation message to thetargeted mediation recipient.
 257. The system of claim 256, wherein thetransit vehicle transceiver is further operative to automaticallygenerate the mediation message as a trigger message for a firesuppression system on the transit vehicle, and provide the mediationmessage to the fire suppression system over the fire suppression systeminterface to cause the fire suppression system to automatically initiatea fire suppression response on the shipping container.
 258. The systemof claim 256, wherein the transit vehicle transceiver is furtheroperative to automatically generate the mediation message as a warningmessage to an operator of the transit vehicle as the targeted mediationrecipient; and provide the warning message to the operator of thetransit vehicle using the display interface of the transit vehicletransceiver.
 259. The system of claim 256, wherein the transit vehicletransceiver is further operative to automatically generate the mediationmessage as a warning message to a logistics crew member of the transitvehicle as the targeted mediation recipient; and provide the warningmessage to the logistics crew member of the transit vehicle using thedisplay interface of the transit vehicle transceiver.
 260. The system ofclaim 259, wherein the warning message reflects the mediation responsepriority.
 261. The system of claim 260, wherein the warning messagecomprises a prompted request for the logistics crew member to initiate aresponsive action for the shipping container.
 262. The system of claim261, wherein the responsive action in the prompted request comprises adirective to inspect the shipping container.
 263. The system of claim261, wherein the responsive action in the prompted request comprises adirective to trigger the fire suppression system after an inspection ofthe shipping container.
 264. The system of claim 256, wherein the mobilemaster node is temporarily mounted to the shipping container within ashipment pouch disposed on the shipping container.
 265. The system ofclaim 256, wherein the mobile master node comprises location circuitrythat allows the mobile master node to self-locate.
 266. The system ofclaim 256, wherein the at least one environmental sensor on each of theID sensor nodes comprises at least one from a group consisting of amovement sensor, an acceleration sensor, an altitude sensor, an attitudesensor, and an orientation sensor.
 267. The system of claim 256, whereinthe at least one environmental sensor on each of the ID sensor nodescomprises at least one from a group consisting of a light sensor and ahumidity sensor.
 268. The system of claim 256, wherein the at least oneenvironmental sensor on each of the ID sensor nodes comprises at leastone from a group consisting of a chemical sensor, a radiation sensor,and a magnetic field sensor.
 269. The system of claim 256, wherein theat least one environmental sensor on each of the ID sensor nodescomprises at least two from a group consisting of a temperature sensor,a barometric pressure sensor, a movement sensor, an acceleration sensor,an altitude sensor, an attitude sensor, an orientation sensor, a lightsensor, a humidity sensor, a chemical sensor, a radiation sensor, and amagnetic field sensor.